Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #654

/assign rhdmalone

@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-63481 has been cloned as Jira Issue OCPBUGS-63521. Will retitle bug to link to clone.
/retitle [release-4.12] OCPBUGS-63521: references to github.com/sclorg/django-ex.git now also refer to the branch

In response to this:

This is an automated cherry-pick of #654

/assign rhdmalone

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.12] OCPBUGS-63481: references to github.com/sclorg/django-ex.git now also refer to the branch [release-4.12] OCPBUGS-63521: references to github.com/sclorg/django-ex.git now also refer to the branch Oct 24, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Oct 24, 2025
@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-63481 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-63481 to target a version in 4.13.0, 4.13.z, but it targets "4.21.0" 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 #654

/assign rhdmalone

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 24, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 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 adambkaplan 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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2025

@openshift-cherrypick-robot: 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/okd-scos-e2e-aws-ovn a2aa05b link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-image-ecosystem a2aa05b link true /test e2e-aws-ovn-image-ecosystem
ci/prow/okd-scos-e2e-aws-ovn-upgrade a2aa05b link false /test okd-scos-e2e-aws-ovn-upgrade
ci/prow/okd-scos-e2e-aws-ovn-builds a2aa05b link false /test okd-scos-e2e-aws-ovn-builds
ci/prow/okd-scos-e2e-aws-ovn-jenkins a2aa05b link false /test okd-scos-e2e-aws-ovn-jenkins
ci/prow/okd-scos-e2e-aws-operator a2aa05b link false /test okd-scos-e2e-aws-operator
ci/prow/e2e-aws-ovn a2aa05b link true /test e2e-aws-ovn
ci/prow/okd-scos-e2e-aws-ovn-image-ecosystem a2aa05b link false /test okd-scos-e2e-aws-ovn-image-ecosystem
ci/prow/e2e-aws-ovn-operator a2aa05b link true /test e2e-aws-ovn-operator

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

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate 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