Skip to content

[release-4.19] OCPBUGS-57035, OPRUN-3925: [Default Catalog Consistency Test] (feat) add check to validate multi-arch support #370

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

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #364

/assign camilamacedo86

/cherrypick release-4.18 release-4.17

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 3, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OPRUN-3925
Jira Issue OCPBUGS-56853 has been cloned as Jira Issue OCPBUGS-57035. Will retitle bug to link to clone.

WARNING: Failed to update the target version, assignee, and sprint for the clone. Please update these fields manually. Full error below:

Full error message. No response returned: Put "https://issues.redhat.com/rest/api/2/issue/OCPBUGS-57035": PUT https://issues.redhat.com/rest/api/2/issue/OCPBUGS-57035 giving up after 5 attempt(s)
/retitle [release-4.19] OCPBUGS-57035, [OPRUN-3925](https://issues.redhat.com//browse/OPRUN-3925): [Default Catalog Consistency Test] (feat) add check to validate multi-arch support

In response to this:

This is an automated cherry-pick of #364

/assign camilamacedo86

/cherrypick release-4.18 release-4.17

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 [release-4.19] OCPBUGS-56853, OPRUN-3925: [Default Catalog Consistency Test] (feat) add check to validate multi-arch support [release-4.19] OCPBUGS-57035, OPRUN-3925: [Default Catalog Consistency Test] (feat) add check to validate multi-arch support Jun 3, 2025
@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 Jun 3, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 3, 2025

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

  • expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.20.0" instead
  • 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.

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.

This pull request references OPRUN-3925 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 story to target the "4.19.0" version, but no target version was set.

In response to this:

This is an automated cherry-pick of #364

/assign camilamacedo86

/cherrypick release-4.18 release-4.17

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 gallettilance and grokspawn June 3, 2025 17:02
Copy link
Contributor

openshift-ci bot commented Jun 3, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign tmshort for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@camilamacedo86
Copy link
Contributor

Closing this one we decided not cherry-pick,

@camilamacedo86
Copy link
Contributor

/close

@openshift-ci openshift-ci bot closed this Jun 3, 2025
Copy link
Contributor

openshift-ci bot commented Jun 3, 2025

@camilamacedo86: Closed this PR.

In response to this:

/close

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.

@camilamacedo86
Copy link
Contributor

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants