Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[release-4.15] ztp: OCPBUGS-30345: OperatorHub.yaml is missing from the ztp source-crs #1843

Merged
merged 1 commit into from Mar 14, 2024
Merged

[release-4.15] ztp: OCPBUGS-30345: OperatorHub.yaml is missing from the ztp source-crs #1843

merged 1 commit into from Mar 14, 2024

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #1839

/assign sabbir-47

@sabbir-47
ztp: OCPBUGS-OCPBUGS-27893: OperatorHub.yaml is missing from the ztp …
e279372 
…source-crs

- MNO clusters requires OperatorHub CR
- Added a common-mno-ranGen.yaml file targeting MNO cluster
- OperatorHub.yaml file added back, and this is only require for MNO cluster

Signed-off-by: Sabbir Hasan <sahasan@redhat.com>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Mar 6, 2024
Merged
@openshift-ci-robot
Copy link
Collaborator

@openshift-cherrypick-robot: Jira Issue OCPBUGS-27893 has been cloned as Jira Issue OCPBUGS-30345. Will retitle bug to link to clone.
/retitle [release-4.15] ztp: OCPBUGS-30345: OperatorHub.yaml is missing from the ztp source-crs

In response to this:

This is an automated cherry-pick of #1839

/assign sabbir-47

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 requested review from fedepaol and yuvalk March 6, 2024 17:55
@openshift-ci openshift-ci bot changed the title [release-4.15] ztp: OCPBUGS-27893: OperatorHub.yaml is missing from the ztp source-crs [release-4.15] ztp: OCPBUGS-30345: OperatorHub.yaml is missing from the ztp source-crs Mar 6, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important 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 Mar 6, 2024
@openshift-ci-robot
Copy link
Collaborator

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-30345, which is invalid:

  • expected dependent Jira Issue OCPBUGS-27893 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

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:

This is an automated cherry-pick of #1839

/assign sabbir-47

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.

@sabbir-47
Copy link
Contributor

/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. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 14, 2024
@openshift-ci-robot
Copy link
Collaborator

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

Requesting review from QA contact:
/cc @yliu127

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.

@openshift-ci openshift-ci bot requested a review from yliu127 March 14, 2024 14:17
@sabbir-47
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 14, 2024
@sabbir-47
Copy link
Contributor

/approve

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 14, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sabbir-47

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 Mar 14, 2024
@sabbir-47
Copy link
Contributor

/test ci

@openshift-merge-bot openshift-merge-bot bot merged commit 2972990 into openshift-kni:release-4.15 Mar 14, 2024
4 checks passed
@openshift-ci-robot
Copy link
Collaborator

@openshift-cherrypick-robot: Jira Issue OCPBUGS-30345: All pull requests linked via external trackers have merged:

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

In response to this:

This is an automated cherry-pick of #1839

/assign sabbir-47

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.

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

@fedepaol fedepaol Awaiting requested review from fedepaol

@yuvalk yuvalk Awaiting requested review from yuvalk

@yliu127 yliu127 Awaiting requested review from yliu127

Assignees

@sabbir-47 sabbir-47

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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.

None yet
3 participants
@openshift-cherrypick-robot @openshift-ci-robot @sabbir-47