Skip to content

[release-4.15] USHIFT-3170: Use RH's Community Operators instead of OperatorHub.io#3364

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.15from
pmtk:olm/change-catalog-source-4.15
May 16, 2024
Merged

[release-4.15] USHIFT-3170: Use RH's Community Operators instead of OperatorHub.io#3364
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.15from
pmtk:olm/change-catalog-source-4.15

Conversation

@pmtk
Copy link
Copy Markdown
Member

@pmtk pmtk commented May 16, 2024

No description provided.

@openshift-ci openshift-ci Bot requested review from jerpeter1 and pliurh May 16, 2024 11:15
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 16, 2024
@pmtk
Copy link
Copy Markdown
Member Author

pmtk commented May 16, 2024

/test metal-periodic-test metal-periodic-test-arm

@pmtk pmtk force-pushed the olm/change-catalog-source-4.15 branch from bc8c91c to 324b9a9 Compare May 16, 2024 13:24
@pmtk
Copy link
Copy Markdown
Member Author

pmtk commented May 16, 2024

/test metal-periodic-test metal-periodic-test-arm

@pmtk pmtk changed the title [release-4.15] Use RH's Community Operators instead of OperatorHub.io [release-4.15] USHIFT-3170: Use RH's Community Operators instead of OperatorHub.io May 16, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 16, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 16, 2024 •
edited by openshift-ci Bot
Loading

@pmtk: This pull request references USHIFT-3170 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.15.z" version, but no target version was set.

Details

In response to this:

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

openshift-ci Bot commented May 16, 2024

@pmtk: 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-sigs/prow repository. I understand the commands that are listed here.

pacevedom
pacevedom approved these changes May 16, 2024
View reviewed changes
Copy link
Copy Markdown
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/label backport-risk-assessed
/lgtm

@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 May 16, 2024
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 16, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pacevedom, pmtk

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

@jogeo
Copy link
Copy Markdown
Contributor

jogeo commented May 16, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci Bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label May 16, 2024
@dhensel-rh
Copy link
Copy Markdown
Contributor

dhensel-rh commented May 16, 2024

/label cherry-pick-approved

@pacevedom
Copy link
Copy Markdown
Contributor

pacevedom commented May 16, 2024

/label jira/valid-bug

@openshift-ci openshift-ci Bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label May 16, 2024
@openshift-merge-bot openshift-merge-bot Bot merged commit 7183329 into openshift:release-4.15 May 16, 2024
@pmtk pmtk deleted the olm/change-catalog-source-4.15 branch May 17, 2024 05:21
@microshift-rebase-script microshift-rebase-script Bot mentioned this pull request Aug 16, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pacevedom pacevedom pacevedom approved these changes

@jerpeter1 jerpeter1 Awaiting requested review from jerpeter1

@pliurh pliurh Awaiting requested review from pliurh

Assignees

@pacevedom pacevedom

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. 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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@pmtk @openshift-ci-robot @jogeo @dhensel-rh @pacevedom