openstack/neutron
Code Issues Proposed changes

Merge "Remove reference of openstack-health"

Browse Source
This commit is contained in:
Zuul 2022-04-06 09:44:07 +00:00 committed by Gerrit Code Review
commit bddf83eaa4
2 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -294,8 +294,8 @@ If the bug report is sound, move next:
issue, make sure that there is at least one patch that 'Closes' the bug
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 Health <http://status.openstack.org/openstack-health/#/>`_
or `OpenStack Logstash <http://logstash.openstack.org/#/dashboard/file/logstash.json>`_.
test over time using
`OpenStack Logstash <http://logstash.openstack.org/#/dashboard/file/logstash.json>`_.
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.
* If the bug is the result of a misuse of the system, mark the bug either

1
doc/source/contributor/stadium/governance.rst
View File

@ -85,7 +85,6 @@ mature OpenStack projects:
* Exhaustive OpenStack CI coverage: unit, functional, and tempest coverage
using OpenStack CI (upstream) resources so that `Grafana <https://grafana.opendev.org/d/f913631585/neutron-failure-rate>`_
and `OpenStack Health <http://status.openstack.org/openstack-health/#/>`_
support is available. Access to CI resources and historical data by the
team is key to ensuring stability and robustness of a project.
In particular, it is of paramount importance to ensure that DB models/migrations