openshift
[release-4.8] Bug 2077100: 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 2077100. Retitling PR to link against new bug. /retitle [release-4.8] Bug 2077100: Fix Web Terminal availability check to verify operator is installed
In response to this:
[release-4.8] 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 2077100, 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 2065804 to target a release in 4.9.0, 4.9.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.8] Bug 2077100: 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.
@debsmita1: This pull request references Bugzilla bug 2077100, which is invalid:
- expected dependent Bugzilla bug 2077141 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
- 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.9.0, 4.9.z, but it targets "4.11.0" instead
- expected dependent Bugzilla bug 2077142 to target a release in 4.9.0, 4.9.z, but it targets "4.10.z" 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: This pull request references Bugzilla bug 2077100, which is invalid:
- expected dependent Bugzilla bug 2077141 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.9.0, 4.9.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: This pull request references Bugzilla bug 2077100, which is invalid:
- expected dependent Bugzilla bug 2077141 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.
/lgtm /label backport-risk-assessed
have verified the changes and works as expected
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 2077100, which is invalid:
- expected dependent Bugzilla bug 2077141 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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
Recalculating validity in case the underlying Bugzilla bug has changed.
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: This pull request references Bugzilla bug 2077100, which is invalid:
- expected dependent Bugzilla bug 2077141 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 2077100, which is invalid:
- expected dependent Bugzilla bug 2077141 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 2077100, which is invalid:
- expected dependent Bugzilla bug 2077141 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 2077100, which is invalid:
- expected dependent Bugzilla bug 2077141 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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
Recalculating validity in case the underlying Bugzilla bug has changed.
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.
/bugzilla refresh
Recalculating validity in case the underlying Bugzilla bug has changed.
@openshift-bot: This pull request references Bugzilla bug 2077100, which is invalid:
- expected dependent Bugzilla bug 2077141 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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
Recalculating validity in case the underlying Bugzilla bug has changed.
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: This pull request references Bugzilla bug 2077100, which is valid.
6 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target release (4.8.z) matches configured target release for branch (4.8.z)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
- dependent bug Bugzilla bug 2077141 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
- dependent Bugzilla bug 2077141 targets the "4.9.z" release, which is one of the valid target releases: 4.9.0, 4.9.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.
@spadgett need your approval on this, @jhadvig already approved but label didn't got added
