Closed aguidirh closed 1 month ago
@aguidirh: This pull request references CLID-122 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 sub-task to target the "4.17.0" version, but no target version was set.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: aguidirh
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@aguidirh: This pull request references CLID-122 which is a valid jira issue.
@aguidirh: This pull request references CLID-122 which is a valid jira issue.
@aguidirh: all tests passed!
Full PR test history. Your PR dashboard.
@aguidirh - Thanks for updating this for us. Just out of curiosity where you able to re-create the hanging problem with this version ?
@lmzuccarelli the tests I did the hang issue did not happen. But as you know this issue does not happen always so maybe it is still there.
@kasturinarra and @zhouying7780 could you please test to see if there is no regression on v1? I tested only v2 flows.
from my side it looks good (all tests are passing) - lets wait for QE to report on regressions
LGTM for me as well :+1: Curious to learn more from your explanation on how to setup the registry log (it does look easier than before).
/lgtm
/cherrypick release-4.16
[ART PR BUILD NOTIFIER]
This PR has been included in build oc-mirror-plugin-container-v4.17.0-202406041111.p0.g765d94b.assembly.stream.el9 for distgit oc-mirror-plugin. All builds following this will include this PR.
/cherrypick release-4.16
/cherry-pick release-4.16
@aguidirh: Jira Issue OCPBUGS-34948: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-34948 has been moved to the MODIFIED state.
Description
This PR upgrades the distribution/distribution to a version released in github (v3.0.0-alpha.1) which is the one recommended by the maintainers.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
MirrorToMirror, MirrorToDisk and DiskToMirror on v2
It is necessary to still run the basic flows on v1.
Expected Outcome
All the flows should finish successfully.