Skip to content

OCPBUGS-55386: Update oc-mirror to use -v2 #1752

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.

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

Merged
merged 1 commit into from
May 16, 2025

Conversation

bfournie
Copy link
Contributor

Use version v2 of oc-mirror. This version has many improvements over v1 but the primary reason for using v2 is that it allows nightly or CI builds to be tested via the release field in the ImageSetConfiguration.

Note that oc-mirror is not currently used in any CI tests and has strictly been used for local testing with the agent-based installer. As a result its not necessary to keep backwards compatibility with v1.

It's expected that oc-mirror will eventually be used for setting up a mirror for disconnected testing instead of 'oc adm release mirror' since its the most common way to set up mirrors by our customers; 'oc adm release mirror' does not provide for installing additional operators.

@bfournie
Copy link
Contributor Author

/cc @andfasano @pawanpinjarkar @rwsu

@openshift-ci openshift-ci bot requested review from andfasano and rwsu April 25, 2025 16:15
Use version v2 of oc-mirror. This version has many improvements over v1
but the primary reason for using v2 is that it allows nightly or CI
builds to be tested via the release field in the ImageSetConfiguration.

Note that oc-mirror is not currently used in any CI tests and has strictly
been used for local testing with the agent-based installer. As a
result its not necessary to keep backwards compatibility with v1.

It's expected that oc-mirror will eventually be used for setting up a
mirror for disconnected testing instead of 'oc adm release mirror'
since its the most common way to set up mirrors by our customers;
'oc adm release mirror' does not provide for installing additional
operators.
@rwsu
Copy link
Contributor

rwsu commented May 12, 2025

/lgtm

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

rwsu commented May 12, 2025

/retest-required

@andfasano
Copy link
Member

/approve

Copy link

openshift-ci bot commented May 15, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano

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 15, 2025
Copy link

openshift-ci bot commented May 15, 2025

@bfournie: 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/e2e-metal-ipi-bm-bond c6dbbd1 link false /test e2e-metal-ipi-bm-bond
ci/prow/e2e-agent-4control-ipv4 c6dbbd1 link false /test e2e-agent-4control-ipv4
ci/prow/e2e-metal-ipi-serial-ovn-ipv6 c6dbbd1 link false /test e2e-metal-ipi-serial-ovn-ipv6
ci/prow/e2e-agent-ha-dualstack c6dbbd1 link false /test e2e-agent-ha-dualstack

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.

@bfournie
Copy link
Contributor Author

/retest-required

@openshift-merge-bot openshift-merge-bot bot merged commit fba144f into openshift-metal3:master May 16, 2025
10 of 14 checks passed
@bfournie bfournie deleted the oc-mirror-v2 branch May 16, 2025 14:06
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.

3 participants