openshift
[release-4.9] Bug 2077141: Fix Web Terminal availability check to verify operator is installed
This is an automated cherry-pick of #11202
/assign amisevsk
@openshift-cherrypick-robot: Bugzilla bug 2065804 has been cloned as Bugzilla bug 2077141. Retitling PR to link against new bug. /retitle [release-4.9] Bug 2077141: Fix Web Terminal availability check to verify operator is installed
In response to this:
[release-4.9] Bug 2065804: Fix Web Terminal availability check to verify operator is installed
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 2077141, which is invalid:
- expected dependent Bugzilla bug 2065804 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
- expected dependent Bugzilla bug 2077142 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
- expected dependent Bugzilla bug 2065804 to target a release in 4.10.0, 4.10.z, but it targets "4.11.0" instead
Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
[release-4.9] Bug 2077141: Fix Web Terminal availability check to verify operator is installed
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-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.
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
@invincibleJai: This pull request references Bugzilla bug 2077141, which is invalid:
- expected dependent Bugzilla bug 2077142 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
- expected dependent Bugzilla bug 2065804 to target a release in 4.10.0, 4.10.z, but it targets "4.11.0" instead
Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/bugzilla refresh
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.
@invincibleJai Any advice on the bugzilla entries here? I can see that something is wrong but don't know how to resolve it.
@invincibleJai: This pull request references Bugzilla bug 2077141, which is invalid:
- expected dependent Bugzilla bug 2077142 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/bugzilla refresh
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.
@invincibleJai Any advice on the bugzilla entries here? I can see that something is wrong but don't know how to resolve it.
I have updated the bugzilla references and now this ticket depends only on 4.10.z. So It'll get merged in order i.e first 4.10.z (https://github.com/openshift/console/pull/11374) needs to get merged and verified(BZ needs to be updated as well) and then only 4.9.z can get in.
@invincibleJai Any advice on the bugzilla entries here? I can see that something is wrong but don't know how to resolve it.
I have updated the bugzilla references and now this ticket depends only on 4.10.z. So It'll get merged in order i.e first 4.10.z (#11374) needs to get merged and verified(BZ needs to be updated as well) and then only 4.9.z can get in.
Verified it on 4.10. Now we can check this one here.
/bugzilla refresh
@jerolimov: This pull request references Bugzilla bug 2077141, which is valid.
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 POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
- dependent bug Bugzilla bug 2077142 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
- dependent Bugzilla bug 2077142 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 @sanketpathak
In response to this:
/bugzilla refresh
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.
/lgtm /label backport-risk-assessed
Have verified the changes and works as expected
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: invincibleJai, jhadvig, openshift-cherrypick-robot
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~pkg/OWNERS~~ [jhadvig]
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 pull requests linked via external trackers have merged:
Bugzilla bug 2077141 has been moved to the MODIFIED state.
In response to this:
[release-4.9] Bug 2077141: Fix Web Terminal availability check to verify operator is installed
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.