Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use mirror-registry tool #60313

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Use mirror-registry tool #60313

wants to merge 1 commit into from

Conversation

MaysaMacedo
Copy link
Contributor

No description provided.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 3, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 3, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MaysaMacedo

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 Jan 3, 2025
@hector-vido
Copy link
Contributor

/retest

@MaysaMacedo MaysaMacedo force-pushed the use-supported-mirror-registry branch from 0037ae0 to be2fd64 Compare January 17, 2025 15:14
@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-master-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: job(s): pull-ci-openshift-installer-master-e2e-openstack-singlestackv6 either don't exist or were not found to be affected, and cannot be rehearsed

@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@MaysaMacedo MaysaMacedo force-pushed the use-supported-mirror-registry branch from 29f1a6c to 267661b Compare January 20, 2025 19:10
@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@MaysaMacedo MaysaMacedo force-pushed the use-supported-mirror-registry branch from 267661b to 54ec07c Compare January 20, 2025 20:26
@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@MaysaMacedo MaysaMacedo force-pushed the use-supported-mirror-registry branch from 54ec07c to 209561e Compare January 20, 2025 22:06
@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@MaysaMacedo MaysaMacedo force-pushed the use-supported-mirror-registry branch from 209561e to fcf18c6 Compare January 21, 2025 01:11
@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@MaysaMacedo MaysaMacedo force-pushed the use-supported-mirror-registry branch from fcf18c6 to 9383c2d Compare January 21, 2025 14:50
@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@MaysaMacedo: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-cluster-capi-operator-main-e2e-openstack-capi-techpreview openshift/cluster-capi-operator presubmit Registry content changed
pull-ci-openshift-cluster-capi-operator-release-4.20-e2e-openstack-capi-techpreview openshift/cluster-capi-operator presubmit Registry content changed
pull-ci-openshift-cluster-capi-operator-release-4.19-e2e-openstack-capi-techpreview openshift/cluster-capi-operator presubmit Registry content changed
pull-ci-openshift-cluster-capi-operator-release-4.18-e2e-openstack-capi-techpreview openshift/cluster-capi-operator presubmit Registry content changed
pull-ci-openshift-cluster-capi-operator-release-4.17-e2e-openstack-capi-techpreview openshift/cluster-capi-operator presubmit Registry content changed
pull-ci-openshift-cluster-capi-operator-release-4.16-e2e-openstack-capi-techpreview openshift/cluster-capi-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-master-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.20-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.19-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.18-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.17-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.16-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.15-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.14-e2e-openstack-kuryr openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.14-e2e-openstack-sdn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.14-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.13-e2e-openstack-kuryr openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.13-e2e-openstack-sdn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.13-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.12-e2e-openstack-kuryr openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.12-e2e-openstack-sdn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.12-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.11-e2e-openstack-kuryr openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.11-e2e-openstack openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-cluster-network-operator-release-4.11-e2e-openstack-ovn openshift/cluster-network-operator presubmit Registry content changed

A total of 985 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@MaysaMacedo
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 4, 2025

@MaysaMacedo: 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/step-registry-shellcheck 0037ae0 link true /test step-registry-shellcheck
ci/rehearse/openshift/installer/main/e2e-openstack-singlestackv6 9383c2d link unknown /pj-rehearse pull-ci-openshift-installer-main-e2e-openstack-singlestackv6

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
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d 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 Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@MaysaMacedo @hector-vido @openshift-ci-robot @openshift-bot