You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the fully disconnected path, I mirrored my images locally, published successfully, and then attempted to publish a second time. The error message reported is not clear:
error: error occurred during publishing, expecting imageset with prefix mirror_seq2: invalid mirror sequence order, want 2, got 1
What did you expect to happen?
It's not immediately clear what the error message means unless I understand the concept of imageset archive file naming. Additionally, I think there are two scenarios here that the error message needs to take into account:
I mistakenly attempted to publish the mirror_seq1 tar file a second time and there's nothing for the CLI to do because everything has been published
I'm attempting to publish a new archive, but something went wrong with the mirror process and there is no mirror_seq2 tar file.
The error message today is written for the second scenario whereas if it were written for the first scenario, it could be something like, "mirror_seq_000000.tar has been previously published. No new work to do."
I'm unsure how to update the error message to take both items into account, so this may be more of a request for better documentation around these scenarios rather than an update to the actual error message in oc-mirror.
How to reproduce it (as minimally and precisely as possible)?
$ oc-mirror --config imageset-config.yaml file://archive<output removed>
$ oc-mirror --from archive/ docker://localhost:5000 --dest-skip-tls<output removed>
$ oc-mirror --from archive/ docker://localhost:5000 --dest-skip-tlsINFO Checking push permissions for localhost:5000 INFO Publishing image set from archive "archive/mirror_seq1_000000.tar" to registry "localhost:5000" INFO Extracting archive archive/mirror_seq1_000000.tar error: error occurred during publishing, expecting imageset with prefix mirror_seq2: invalid mirror sequence order, want 2, got 1
Anything else we need to know?
Enter text here.
References
Enter text here.
The text was updated successfully, but these errors were encountered:
@nschambu Thanks for the feedback here. I have an open docs update PR #415 to incorporate some information around metadata handling and I can add in some information about sequence numbers and naming here. The is really no way to distinguish between the two scenarios above since the publishing operations are completely separate from the imageset creation. One thing I do want to note is that oc-mirror does not currently handle being passed multiple imageset sequences during one publish, which I can also add in the docs.
Version
What happened?
Using the fully disconnected path, I mirrored my images locally, published successfully, and then attempted to publish a second time. The error message reported is not clear:
What did you expect to happen?
It's not immediately clear what the error message means unless I understand the concept of imageset archive file naming. Additionally, I think there are two scenarios here that the error message needs to take into account:
The error message today is written for the second scenario whereas if it were written for the first scenario, it could be something like, "mirror_seq_000000.tar has been previously published. No new work to do."
I'm unsure how to update the error message to take both items into account, so this may be more of a request for better documentation around these scenarios rather than an update to the actual error message in oc-mirror.
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
Enter text here.
References
Enter text here.
The text was updated successfully, but these errors were encountered: