Skip to content

OCPBUGS-24587: Clear (existing) error cond from Subscription, once error resolved - #680

Closed
anik120 wants to merge 1 commit into
openshift:masterfrom
anik120:subs-res-cond-clear
Closed

OCPBUGS-24587: Clear (existing) error cond from Subscription, once error resolved#680
anik120 wants to merge 1 commit into
openshift:masterfrom
anik120:subs-res-cond-clear

Conversation

@anik120

@anik120 anik120 commented Feb 2, 2024

Copy link
Copy Markdown
Contributor

Upstream fix: operator-framework/operator-lifecycle-manager#3166

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 54da66a9996632315827ba37e14823de6405b4d9

…ror resolved

Upstream fix: operator-framework/operator-lifecycle-manager#3166

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 54da66a9996632315827ba37e14823de6405b4d9

Signed-off-by: Anik Bhattacharjee <anbhatta@redhat.com>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 2, 2024
@openshift-ci-robot

Copy link
Copy Markdown

@anik120: This pull request references Jira Issue OCPBUGS-24587, which is invalid:

  • expected the bug to target the "4.16.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.

Details

In response to this:

Upstream fix: operator-framework/operator-lifecycle-manager#3166

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 54da66a9996632315827ba37e14823de6405b4d9

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Feb 2, 2024

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 2, 2024
@anik120

anik120 commented Feb 2, 2024

Copy link
Copy Markdown
Contributor Author

Oops this is being pulled by the automated script in #679

@anik120 anik120 closed this Feb 2, 2024
@openshift-ci-robot

Copy link
Copy Markdown

@anik120: This pull request references Jira Issue OCPBUGS-24587. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

Details

In response to this:

Upstream fix: operator-framework/operator-lifecycle-manager#3166

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 54da66a9996632315827ba37e14823de6405b4d9

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Feb 2, 2024

Copy link
Copy Markdown
Contributor

@anik120: 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/verify 458dccc link true /test verify

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants