[OSPRH-19828] Improve consistency of condition severity usage#1599
Conversation
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/217ef7ffea584648be359ef4af798442 ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 19m 57s |
😖 /test openstack-operator-build-deploy-kuttl |
🙄 /test openstack-operator-build-deploy-kuttl |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abays, stuggi The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Surely you can't be serious. Again?! /test openstack-operator-build-deploy-kuttl |
😡 /test openstack-operator-build-deploy-kuttl |
9ad9305
into
openstack-k8s-operators:main
|
/cherry-pick 18.0-fr3 |
|
@abays: #1599 failed to apply on top of branch "18.0-fr3": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
First pass of trying to achieve greater consistency of condition
Severityacross all our operators.Jira: https://issues.redhat.com/browse/OSPRH-19828