Skip to content

OCPBUGS-59258: 🐛 add catalog-operator control-plane-specific tolerations to unpack jobs #1037

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: release-4.19
Choose a base branch
from

Conversation

grokspawn
Copy link
Contributor

  • add catalog-operator control-plane-specific tolerations to unpack jobs
  • refactored common in test

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 57e6b8c8b381be1d6432718905b9825495836470

…obs (#3606)

* add catalog-operator control-plane-specific tolerations to unpack jobs

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

* refactored common in test

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

---------

Signed-off-by: grokspawn <[email protected]>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 57e6b8c8b381be1d6432718905b9825495836470
Copy link
Contributor

openshift-ci bot commented Jul 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn

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

The pull request process is described here

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 Jul 11, 2025
@grokspawn
Copy link
Contributor Author

/jira cherrypick OCPBUGS-58349

@openshift-ci-robot
Copy link

@grokspawn: Jira Issue OCPBUGS-58349 has been cloned as Jira Issue OCPBUGS-59258. Will retitle bug to link to clone.
/retitle OCPBUGS-59258: 🐛 add catalog-operator control-plane-specific tolerations to unpack jobs

In response to this:

/jira cherrypick OCPBUGS-58349

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 changed the title 🐛 add catalog-operator control-plane-specific tolerations to unpack jobs OCPBUGS-59258: 🐛 add catalog-operator control-plane-specific tolerations to unpack jobs Jul 11, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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 Jul 11, 2025
@openshift-ci-robot
Copy link

@grokspawn: This pull request references Jira Issue OCPBUGS-59258, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-58349 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead
  • expected dependent Jira Issue OCPBUGS-58349 to target a version in 4.20.0, 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:

  • add catalog-operator control-plane-specific tolerations to unpack jobs
  • refactored common in test

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 57e6b8c8b381be1d6432718905b9825495836470

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.

@grokspawn
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

@grokspawn: This pull request references Jira Issue OCPBUGS-59258, which is invalid:

  • expected dependent Jira Issue OCPBUGS-58349 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead
  • expected dependent Jira Issue OCPBUGS-58349 to target a version in 4.20.0, 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 openshift-eng/jira-lifecycle-plugin repository.

Copy link
Contributor

openshift-ci bot commented Jul 11, 2025

@grokspawn: The following tests 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-olm 81f63f7 link true /test e2e-gcp-olm
ci/prow/okd-scos-e2e-aws-ovn 81f63f7 link false /test okd-scos-e2e-aws-ovn

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-sigs/prow 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/severity-critical Referenced Jira bug's severity is critical 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