OCPBUGS-1696: Handle missing BMH for Node gracefully
Backport of https://github.com/openshift/console/pull/11492
@rawagner: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.
In response to this:
Handle missing BMH for Node gracefully
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.
@rawagner: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.
In response to this:
OCPBUGS-1975: Handle missing BMH for Node gracefully
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.
@rawagner: This pull request references Jira Issue OCPBUGS-1975, which is valid. The bug has been moved to the POST state.
6 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.10.z) matches configured target version for branch (4.10.z)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
- dependent bug Bugzilla Bug 2090993 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
- dependent Bugzilla Bug 2090993 targets the "4.11.0" version, which is one of the valid target versions: 4.11.0, 4.11.z
- bug has dependents
Requesting review from QA contact: /cc @yanpzhan
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
Backport of https://github.com/openshift/console/pull/11492
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.
@rawagner: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.
Retaining the bugzilla/valid-bug label as it was manually added.
In response to this:
OCPBUGS-1696: Handle missing BMH for Node gracefully
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.
@rawagner: This pull request references Jira Issue OCPBUGS-1696, which is invalid:
- expected the bug to target the "4.10.z" version, but no target version was set
- expected Jira Issue OCPBUGS-1696 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
Backport of https://github.com/openshift/console/pull/11492
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.
/jira refresh
@rawagner: This pull request references Jira Issue OCPBUGS-1696, which is invalid:
- expected the bug to target the "4.10.z" version, but no target version was set
- expected Jira Issue OCPBUGS-1696 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira 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.
/jira refresh
@rawagner: This pull request references Jira Issue OCPBUGS-1696, which is invalid:
- expected Jira Issue OCPBUGS-1696 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira 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.
/jira refresh
@rawagner: This pull request references Jira Issue OCPBUGS-1696, which is valid. The bug has been moved to the POST state.
6 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.10.z) matches configured target version for branch (4.10.z)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
- dependent bug Bugzilla Bug 2090993 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
- dependent Bugzilla Bug 2090993 targets the "4.11.0" version, which is one of the valid target versions: 4.11.0, 4.11.z
- bug has dependents
Requesting review from QA contact: /cc @yapei
In response to this:
/jira 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.
/retest
/retest
@yapei @yanpzhan can you please take a look ?
/label backport-risk-assessed /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jhadvig, jtomasek, rawagner
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/OWNERS~~ [jhadvig,rawagner]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/label qe-approved
/label cherry-pick-approved
/retest-required
Remaining retests: 0 against base HEAD 10c9539c1654d28eed42a2519e589c2afe7418b6 and 2 for PR HEAD a3e33bebe910e8efbc3007d0b1278673b04b0d61 in total
/retest
@rawagner: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-1696 has been moved to the MODIFIED state.
In response to this:
Backport of https://github.com/openshift/console/pull/11492
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.