Skip to content

Conversation

@rhdmalone
Copy link
Contributor

references to github.com/sclorg/django-ex.git now also refer to the branch

@openshift-ci openshift-ci bot requested review from adambkaplan and shannon October 23, 2025 15:39
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 23, 2025
@rhdmalone rhdmalone changed the title references to github.com/sclorg/django-ex.git now also refer to the branch OCPBUGS-63481: references to github.com/sclorg/django-ex.git now also refer to the branch Oct 23, 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 23, 2025
@openshift-ci-robot
Copy link
Contributor

@rhdmalone: This pull request references Jira Issue OCPBUGS-63481, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (aroyo@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

references to github.com/sclorg/django-ex.git now also refer to the branch

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/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 23, 2025
@rhdmalone
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@rhdmalone: This pull request references Jira Issue OCPBUGS-63481, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (aroyo@redhat.com), skipping review request.

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.

@aroyoredhat
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aroyoredhat, rhdmalone

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:
  • OWNERS [aroyoredhat,rhdmalone]

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 23, 2025

@rhdmalone: The following test 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 edf82c6 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.

@aroyoredhat
Copy link
Contributor

/verified

@openshift-ci-robot
Copy link
Contributor

@aroyoredhat: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

In response to this:

/verified

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.

@aroyoredhat
Copy link
Contributor

/verified by aroyoredhat

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 23, 2025
@openshift-ci-robot
Copy link
Contributor

@aroyoredhat: This PR has been marked as verified by aroyoredhat.

In response to this:

/verified by aroyoredhat

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-merge-bot openshift-merge-bot bot merged commit 14236f8 into openshift:main Oct 23, 2025
10 of 11 checks passed
@openshift-ci-robot
Copy link
Contributor

@rhdmalone: Jira Issue Verification Checks: Jira Issue OCPBUGS-63481
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-63481 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

references to github.com/sclorg/django-ex.git now also refer to the branch

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.

@rhdmalone
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.20

@openshift-ci openshift-ci bot added 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. labels Oct 24, 2025
@openshift-cherrypick-robot

@rhdmalone: new pull request created: #655

In response to this:

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.20

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.

@rhdmalone
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.19

@openshift-cherrypick-robot

@rhdmalone: new pull request created: #656

In response to this:

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.19

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.

@rhdmalone
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.18

@openshift-cherrypick-robot

@rhdmalone: new pull request created: #657

In response to this:

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.18

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.

@rhdmalone
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.17

@openshift-cherrypick-robot

@rhdmalone: new pull request created: #658

In response to this:

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick 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 kubernetes-sigs/prow repository.

@rhdmalone
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.16

@openshift-cherrypick-robot

@rhdmalone: new pull request created: #659

In response to this:

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.16

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.

@rhdmalone
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.15

@openshift-cherrypick-robot

@rhdmalone: new pull request created: #660

In response to this:

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.15

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.

@rhdmalone
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.14

@openshift-cherrypick-robot

@rhdmalone: new pull request created: #661

In response to this:

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.14

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.

@rhdmalone
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.13

@openshift-cherrypick-robot

@rhdmalone: new pull request created: #662

In response to this:

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.13

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.

@rhdmalone
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.12

@openshift-cherrypick-robot

@rhdmalone: new pull request created: #663

In response to this:

/label backport-risk-assessed
/label cherry-pick-approved
/cherrypick release-4.12

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.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.21.0-0.nightly-2025-10-25-183621

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. 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/severity-moderate Referenced Jira bug's severity is moderate 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants