Skip to content

Conversation

@pcbailey
Copy link

@pcbailey pcbailey commented Dec 17, 2025

This PR fixes the tests broken by #111

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 17, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 17, 2025

@pcbailey: This pull request references CNV-66757 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 epic to target either version "4.22." or "openshift-4.22.", but it targets "CNV v4.21.0" instead.

Details

In response to this:

This PR fixes the tests broken by #111

Jira: https://issues.redhat.com/browse/CNV-66757

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 avivtur and yaacov December 17, 2025 13:08
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 17, 2025
@pcbailey pcbailey changed the title CNV-66757: Fix broken tests Fix broken tests Dec 17, 2025
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 17, 2025
@openshift-ci-robot
Copy link

@pcbailey: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

This PR fixes the tests broken by #111

Jira: https://issues.redhat.com/browse/CNV-66757

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.

@galkremer1
Copy link
Member

/retest

2 similar comments
@pcbailey
Copy link
Author

/retest

@pcbailey
Copy link
Author

/retest

@pcbailey pcbailey force-pushed the bug--fix-tests branch 3 times, most recently from 136c7b8 to 83add0d Compare January 8, 2026 14:54
@pcbailey
Copy link
Author

pcbailey commented Jan 9, 2026

/retest

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 9, 2026
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 12, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 13, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pcbailey, upalatucci

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:
  • OWNERS [pcbailey,upalatucci]

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

openshift-ci bot commented Jan 13, 2026

@pcbailey: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit cf7561c into openshift:main Jan 13, 2026
3 checks passed
@upalatucci
Copy link

/cherry-pick releasse-4.21

@openshift-cherrypick-robot

@upalatucci: cannot checkout releasse-4.21: error checking out "releasse-4.21": exit status 1 error: pathspec 'releasse-4.21' did not match any file(s) known to git

Details

In response to this:

/cherry-pick releasse-4.21

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.

@upalatucci
Copy link

/cherry-pick release-4.21

@openshift-cherrypick-robot

@upalatucci: new pull request created: #151

Details

In response to this:

/cherry-pick release-4.21

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.

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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants