Skip to content

WIP: WRKLDS-1713: Migrate to distribution/[email protected] #2036

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

tchap
Copy link
Contributor

@tchap tchap commented Jun 10, 2025

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 10, 2025

@tchap: This pull request references WRKLDS-1713 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 story to target the "4.20.0" version, but no target version was set.

In response to this:

Blocked by openshift/library-go#1972

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-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 10, 2025
@tchap tchap changed the title WRKLDS-1713: WIP: Migrate to distribution/[email protected] WIP: WRKLDS-1713: Migrate to distribution/[email protected] Jun 10, 2025
@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 Jun 10, 2025
@openshift-ci openshift-ci bot requested review from ardaguclu and deads2k June 10, 2025 20:58
Copy link
Contributor

openshift-ci bot commented Jun 10, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tchap
Once this PR has been reviewed and has the lgtm label, please assign atiratree for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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-robot
Copy link

openshift-ci-robot commented Jun 10, 2025

@tchap: This pull request references WRKLDS-1713 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 story to target the "4.20.0" version, but no target version was set.

In response to this:

Blocked by openshift/library-go#1972

It may also be necessary to backport 568b70b

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
Copy link

openshift-ci-robot commented Jun 10, 2025

@tchap: This pull request references WRKLDS-1713 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 story to target the "4.20.0" version, but no target version was set.

In response to this:

Blocked by openshift/library-go#1972

It may also be necessary to backport 568b70b , or it can be done when actually porting oc-mirror to the current oc.

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.

@tchap tchap force-pushed the prune-registry-client branch from 952297c to 44957b5 Compare June 10, 2025 21:04
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 10, 2025

@tchap: This pull request references WRKLDS-1713 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 story to target the "4.20.0" version, but no target version was set.

In response to this:

Blocked by openshift/library-go#1972

It may also be necessary to backport 568b70b , or it can be done when actually porting oc-mirror to the current oc.

Other than cosmetic changes, support for schema1 is dropped here since it's deprecated and no longer supported in distribution/v3.

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.

@ardaguclu
Copy link
Member

There are many bits in this PR moving around (k8s bumps, library-go changes, deprecations). It is very hard to trace the code changes. Would it be better to drop schemav1 support in a separate clean PR?

@tchap
Copy link
Contributor Author

tchap commented Jun 11, 2025

There are many bits in this PR moving around (k8s bumps, library-go changes, deprecations). It is very hard to trace the code changes. Would it be better to drop schemav1 support in a separate clean PR?

@ardaguclu Yes, it's certainly possible to drop it is a separate PR. This actually just contains all changes necessary to migrate to distribution/[email protected], but it may make sense to drop this functionality separately so that it is actually possible to review. I will proceed with that.

@tchap
Copy link
Contributor Author

tchap commented Jun 11, 2025

Removing schema1 in #2037

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 11, 2025

@tchap: This pull request references WRKLDS-1713 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 story to target the "4.20.0" version, but no target version was set.

In response to this:

Blocked by openshift/library-go#1972

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.

@tchap tchap force-pushed the prune-registry-client branch from 86b29c7 to 9dc465d Compare June 12, 2025 12:06
@tchap
Copy link
Contributor Author

tchap commented Jun 12, 2025

Rebased onto main so schema1 changes are no longer a part of this PR.

@tchap
Copy link
Contributor Author

tchap commented Jun 16, 2025

/retest

@tchap tchap force-pushed the prune-registry-client branch 3 times, most recently from 5afabe9 to 0dbb5d9 Compare June 16, 2025 13:58
@tchap
Copy link
Contributor Author

tchap commented Jun 16, 2025

The failing required test prints

go: go.mod requires go >= 1.23.7 (running go 1.23.6; GOTOOLCHAIN=local)

so I guess the issue with required Go version is not gone yet.

@tchap
Copy link
Contributor Author

tchap commented Jun 17, 2025

/retest-required

@tchap
Copy link
Contributor Author

tchap commented Jun 17, 2025

We have to wait for the build images to be updated or distribution/distribution#4637 (comment)

@tchap
Copy link
Contributor Author

tchap commented Jun 17, 2025

/retest-required

@tchap tchap force-pushed the prune-registry-client branch from 57ff7c3 to 3926855 Compare June 20, 2025 08:36
@tchap tchap force-pushed the prune-registry-client branch from 3926855 to 46dd19d Compare June 20, 2025 08:49
Copy link
Contributor

openshift-ci bot commented Jun 20, 2025

@tchap: 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 46dd19d 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants