-
Bug
-
Resolution: Done-Errata
-
Major
-
4.13.z, 4.12.z, 4.14.z
Description of problem:
It's pretty often to fail "oc mirror" with: error: invalid mirror sequence order, want X, got Y The only reliable way to fix it is to just begin everything from scratch, e.g. clearing is needed (delete all directories like oc-mirror-workspace/ and the whole target repository).
Version-Release number of selected component (if applicable):
4.12.z, 4.13.z, 4.14.z
How reproducible:
Sometimes, for example when some network or registries' disturbances occur. Or intentional ctrl+c for "oc mirror" in some specific moment (when already some changes are made in .metadata.json on client or remote registry defined in storageConfig)
Steps to Reproduce:
1. Initial mirror with oc mirror and a config file with ImageSetConfiguration 2. waiting on chanages with images OR adding/removing operators 3. oc mirror run again and fails
Actual results:
Fails: looking for metadata file at "publish/.metadata.json" Checking metadata sequence number error: invalid mirror sequence order, want 2, got 3
Expected results:
It can overcome the issues, maybe operations should be atomic and sequence numbers are incremented when the whole operation is successful.
Additional info:
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update