Skip to content

Conversation

@perdasilva
Copy link
Contributor

Update the CPC dependency to fix an ART issue that is impeding OLM from being released

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 20, 2023

@perdasilva: 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.

Details

In response to this:

[release-4.12] update cluster policy operator dependency

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
Copy link
Contributor

openshift-ci bot commented Feb 20, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

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 20, 2023
@perdasilva perdasilva changed the title [release-4.12] update cluster policy operator dependency OCPBUGS-7769: [release-4.12] update cluster policy operator dependency Feb 20, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 20, 2023

@perdasilva: 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.

Details

In response to this:

OCPBUGS-7769: [release-4.12] update cluster policy operator dependency

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-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 20, 2023
@openshift-ci-robot
Copy link

@perdasilva: This pull request references Jira Issue OCPBUGS-7769, which is invalid:

  • expected dependent Jira Issue OCPBUGS-7754 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is New 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.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Update the CPC dependency to fix an ART issue that is impeding OLM from being released

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.

@perdasilva
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

@perdasilva: This pull request references Jira Issue OCPBUGS-7769, which is invalid:

  • expected dependent Jira Issue OCPBUGS-7754 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is MODIFIED 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.

Details

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.

@perdasilva
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

@perdasilva: This pull request references Jira Issue OCPBUGS-7769, which is invalid:

  • expected dependent Jira Issue OCPBUGS-7754 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is POST 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.

Details

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.

@perdasilva
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 20, 2023
@openshift-ci-robot
Copy link

@perdasilva: This pull request references Jira Issue OCPBUGS-7769, 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.12.z) matches configured target version for branch (4.12.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-7754 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-7754 targets the "4.13.0" version, which is one of the valid target versions: 4.13.0
  • bug has dependents

Requesting review from QA contact:
/cc @jianzhangbjz

Details

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.

@openshift-ci openshift-ci bot requested a review from jianzhangbjz February 20, 2023 17:02
@perdasilva
Copy link
Contributor Author

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 20, 2023
@perdasilva
Copy link
Contributor Author

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 20, 2023

@perdasilva: all tests passed!

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.

@bparees bparees added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 21, 2023
@bparees
Copy link
Contributor

bparees commented Feb 21, 2023

nothing for QE to validate here so adding cherry-pick-approved

@bparees
Copy link
Contributor

bparees commented Feb 21, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 21, 2023
@openshift-merge-robot openshift-merge-robot merged commit 4d5f78f into openshift:release-4.12 Feb 21, 2023
@openshift-ci-robot
Copy link

@perdasilva: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-7769 has been moved to the MODIFIED state.

Details

In response to this:

Update the CPC dependency to fix an ART issue that is impeding OLM from being released

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-bot pushed a commit to openshift-bot/operator-framework-olm that referenced this pull request Dec 18, 2025
* add Release version as an optional field in the CSV

Signed-off-by: grokspawn <[email protected]>
Assisted-by: claude

* review resolutions

Signed-off-by: grokspawn <[email protected]>

---------

Signed-off-by: grokspawn <[email protected]>
Upstream-repository: api
Upstream-commit: f65ea7e8cacbcb5f5f2ba88ddc4bc82f67ab1794
openshift-bot pushed a commit to openshift-bot/operator-framework-olm that referenced this pull request Dec 19, 2025
* add Release version as an optional field in the CSV

Signed-off-by: grokspawn <[email protected]>
Assisted-by: claude

* review resolutions

Signed-off-by: grokspawn <[email protected]>

---------

Signed-off-by: grokspawn <[email protected]>
Upstream-repository: api
Upstream-commit: f65ea7e8cacbcb5f5f2ba88ddc4bc82f67ab1794
openshift-bot pushed a commit to openshift-bot/operator-framework-olm that referenced this pull request Dec 20, 2025
* add Release version as an optional field in the CSV

Signed-off-by: grokspawn <[email protected]>
Assisted-by: claude

* review resolutions

Signed-off-by: grokspawn <[email protected]>

---------

Signed-off-by: grokspawn <[email protected]>
Upstream-repository: api
Upstream-commit: f65ea7e8cacbcb5f5f2ba88ddc4bc82f67ab1794
openshift-bot pushed a commit to openshift-bot/operator-framework-olm that referenced this pull request Dec 25, 2025
* add Release version as an optional field in the CSV

Signed-off-by: grokspawn <[email protected]>
Assisted-by: claude

* review resolutions

Signed-off-by: grokspawn <[email protected]>

---------

Signed-off-by: grokspawn <[email protected]>
Upstream-repository: api
Upstream-commit: f65ea7e8cacbcb5f5f2ba88ddc4bc82f67ab1794
openshift-bot pushed a commit to openshift-bot/operator-framework-olm that referenced this pull request Jan 1, 2026
* add Release version as an optional field in the CSV

Signed-off-by: grokspawn <[email protected]>
Assisted-by: claude

* review resolutions

Signed-off-by: grokspawn <[email protected]>

---------

Signed-off-by: grokspawn <[email protected]>
Upstream-repository: api
Upstream-commit: f65ea7e8cacbcb5f5f2ba88ddc4bc82f67ab1794
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants