openstack/neutron
Code Issues Proposed changes

Update bug triage documentation

Browse Source 
logstash.openstack.org is deprecated
On os discuss was anounced new service - OpenSearch [1]

1)
http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028346.html

Change-Id: Id0ca10e959f47c857e673ec621a18e56835e3440
This commit is contained in:
Nurmatov Mamatisa 2022-04-29 10:37:26 +03:00
parent f15baf16dd
commit a9b8253db4
2 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/source/contributor/policies/bugs.rst
View File

@ -72,7 +72,7 @@ moving down the resolution pipeline.
During the period a member acts as bug deputy, he/she is expected to watch
bugs filed against the Neutron projects (as listed above) and do a first
screening to determine potential severity, tagging, logstash queries, other
screening to determine potential severity, tagging, opensearch queries, other
affected projects, affected releases, etc.
From time to time bugs will be filed and auto-assigned by members of the
@ -295,9 +295,10 @@ If the bug report is sound, move next:
or document/question what it takes to mark the bug as fixed.
* If the bug indicates test or gate failure, look at the failures for that
test over time using
`OpenStack Logstash <http://logstash.openstack.org/#/dashboard/file/logstash.json>`_.
`OpenStack OpenSearch <https://opensearch.logs.openstack.org/_dashboards/app/discover?security_tenant=global>`_.
This can help to validate whether the bug identifies an issue that is
occurring all of the time, some of the time, or only for the bug submitter.
To use OpenSearch please check `documentation <https://docs.openstack.org/project-team-guide/testing.html#checking-status-of-other-job-results>`_.
* If the bug is the result of a misuse of the system, mark the bug either
as 'Won't fix', or 'Opinion' if you are still on the fence and need
other people's input.

9
doc/source/contributor/policies/gate-failure-triage.rst
View File

@ -9,9 +9,10 @@ Spotting Gate Failures
This can be achieved using several tools:
* `Grafana dashboard <https://grafana.opendev.org/d/f913631585/neutron-failure-rate>`_
* `logstash <http://logstash.openstack.org/>`_
* `OpenSearch <https://opensearch.logs.openstack.org/_dashboards/app/discover?security_tenant=global>`_
For checking gate failures with logstash the following query will return failures for a specific job:
For checking gate failures with opensearch please see `documentation <https://docs.openstack.org/project-team-guide/testing.html#checking-status-of-other-job-results>`_.
The following query will return failures for a specific job:
> build_status:FAILURE AND message:Finished AND build_name:"check-tempest-dsvm-neutron" AND build_queue:"gate"
@ -51,8 +52,8 @@ Troubleshooting Tempest jobs
1. If there is a failure in devstack-gate-cleanup-host.txt it's likely to be an infra issue.
2. If the failure is in devstacklog.txt it could a devstack, neutron, or infra issue.
3. However, most of the time the failure is in one of the tempest tests. Take note of the error message and go to
logstash.
4. On logstash, search for occurrences of this error message, and try to identify the root cause for the failure
opensearch.
4. On opensearch, search for occurrences of this error message, and try to identify the root cause for the failure
(see below).
5. File a bug for this failure, and push an :ref:`Elastic Recheck Query <elastic-recheck-query>` for it.
6. If you are confident with the area of this bug, and you have time, assign it to yourself; otherwise look for an