Skip to content

Conversation

nrb
Copy link

@nrb nrb commented May 12, 2025

This is to support renaming the master branch to main.

Counterpart to openshift/release#62707

/hold

Hold for CRT to coordinate merging of all relevant PRs.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels May 12, 2025
@openshift-ci-robot
Copy link

@nrb: This pull request references Jira Issue OCPBUGS-53005, which is valid.

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

Requesting review from QA contact:
/cc @sunzhaohua2

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

In response to this:

This is to support renaming the master branch to main.

Counterpart to openshift/release#62707

/hold

Hold for CRT to coordinate merging of all relevant PRs.

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 sunzhaohua2 May 12, 2025 17:01
@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 12, 2025
@openshift-ci openshift-ci bot requested review from elmiko and theobarberbany May 12, 2025 17:02
Copy link

openshift-ci bot commented May 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nrb

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 May 12, 2025
@nrb
Copy link
Author

nrb commented May 12, 2025

Tests are failing due to the renaming change made here; the change to main will have to happen first.

/override ci/prow/e2e-aws-capi-techpreview ci/prow/e2e-azure-capi-techpreview ci/prow/e2e-gcp-capi-techpreview ci/prow/e2e-openstack-capi-techpreview ci/prow/e2e-vsphere-capi-techpreview

Copy link

openshift-ci bot commented May 12, 2025

@nrb: Overrode contexts on behalf of nrb: ci/prow/e2e-aws-capi-techpreview, ci/prow/e2e-azure-capi-techpreview, ci/prow/e2e-gcp-capi-techpreview, ci/prow/e2e-openstack-capi-techpreview, ci/prow/e2e-vsphere-capi-techpreview

In response to this:

Tests are failing due to the renaming change made here; the change to main will have to happen first.

/override ci/prow/e2e-aws-capi-techpreview ci/prow/e2e-azure-capi-techpreview ci/prow/e2e-gcp-capi-techpreview ci/prow/e2e-openstack-capi-techpreview ci/prow/e2e-vsphere-capi-techpreview

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.

Copy link

openshift-ci bot commented May 12, 2025

@nrb: 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 a6b27df 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.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 11, 2025
@theobarberbany
Copy link

@nrb do we want to do this still? happy to approve / review if we do! :)

@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 28, 2025
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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants