console
console copied to clipboard
openshift
[release-4.9] Bug 2094244: Add 'Unavailable' status to clusteroperator status filter
This is an automated cherry-pick of #11619
/assign jhadvig
@openshift-cherrypick-robot: Bugzilla bug 2092168 has been cloned as Bugzilla bug 2094244. Retitling PR to link against new bug. /retitle [release-4.9] Bug 2094244: Add 'Unavailable' status to clusteroperator status filter
In response to this:
[release-4.9] Bug 2092168: Add 'Unavailable' status to clusteroperator status filter
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/test-infra repository.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@openshift-cherrypick-robot: This pull request references Bugzilla bug 2094244, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.
6 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target release (4.9.z) matches configured target release for branch (4.9.z)
- bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
- dependent bug Bugzilla bug 2092168 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
- dependent Bugzilla bug 2092168 targets the "4.10.z" release, which is one of the valid target releases: 4.10.0, 4.10.z
- bug has dependents
Requesting review from QA contact: /cc @yapei
In response to this:
[release-4.9] Bug 2094244: Add 'Unavailable' status to clusteroperator status filter
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/test-infra repository.
/label qe-approved
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jerolimov, openshift-cherrypick-robot
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/OWNERS~~ [jerolimov]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@openshift-cherrypick-robot: all tests passed!
Full PR test history. Your PR dashboard.
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/test-infra repository. I understand the commands that are listed here.
@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:
Bugzilla bug 2094244 has been moved to the MODIFIED state.
In response to this:
[release-4.9] Bug 2094244: Add 'Unavailable' status to clusteroperator status filter
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/test-infra repository.