openshift
OCPBUGS-1573: Show Operand status as `Terminating` for resources undergoing deletion
/retitle OCPBUGS-1573: Show Operand status as Terminating for resources undergoing deletion
@debjyoti-pandit: This pull request references Jira Issue OCPBUGS-1573, which is invalid:
- expected the bug to target the "4.12.0" version, but no target version was set
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:
fixes: https://bugzilla.redhat.com/show_bug.cgi?id=2106636
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.
@debjyoti-pandit: This pull request references Jira Issue OCPBUGS-1573, which is invalid:
- expected the bug to target the "4.12.0" version, but no target version was set
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.
@debjyoti-pandit: This pull request references Jira Issue OCPBUGS-1573, which is invalid:
- expected the bug to target the "4.12.0" version, but no target version was set
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.
@bipuladh: This pull request references Jira Issue OCPBUGS-1573, which is valid. The bug has been moved to the POST state.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.12.0) matches configured target version for branch (4.12.0)
- bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bipuladh, debjyoti-pandit, SanjalKatiyar, spadgett
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~frontend/packages/operator-lifecycle-manager/OWNERS~~ [spadgett]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@debjyoti-pandit: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-gcp-console | c2eb090530d33bb36517fa4e0bdb20c87f228f99 | link | true | /test e2e-gcp-console |
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.
/bugzilla refresh
The requirements for Bugzilla bugs have changed (BZs linked to PRs on main branch need to target OCP 4.12), recalculating validity.
@openshift-bot: 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:
/bugzilla refresh
The requirements for Bugzilla bugs have changed (BZs linked to PRs on main branch need to target OCP 4.12), recalculating validity.
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
The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target OCP 4.12), recalculating validity.
@openshift-bot: This pull request references Jira Issue OCPBUGS-1573, which is invalid:
- expected the bug to target the "4.13.0" version, but it targets "4.12.0" instead
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
The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target OCP 4.12), recalculating validity.
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.
The changes correspond to the -
https://bugzilla.redhat.com/show_bug.cgi?id=2106636 https://issues.redhat.com/browse/OCPBUGS-1573
And need to go with 4.13
@debjyoti-pandit: This pull request references Jira Issue OCPBUGS-1573, which is valid.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.13.0) matches configured target version for branch (4.13.0)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
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-required
Remaining retests: 0 against base HEAD f80bf5be3d001dc81545e6f4ca3e21d38d720835 and 2 for PR HEAD c2eb090530d33bb36517fa4e0bdb20c87f228f99 in total
/retest-required
Remaining retests: 0 against base HEAD 834e70bd8fa90a2bbc1da4e7d9dd8d493a453a2c and 1 for PR HEAD c2eb090530d33bb36517fa4e0bdb20c87f228f99 in total
/retest-required
Remaining retests: 0 against base HEAD 40413bf269cac7985f83fea0a05561de879752e0 and 0 for PR HEAD c2eb090530d33bb36517fa4e0bdb20c87f228f99 in total