-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
Informational
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
oc-mirror tool creates the same name for the tar file on consecutive runs overwriting the file each time. This makes it very difficult for customers to know when the file was created, what's in the file contents (version of Openshift pulled, operators, etc).
Version-Release number of selected component (if applicable):
4.20
How reproducible:
Happens every time oc-mirror is run
Steps to Reproduce:
1. Create an imageset-config file with any amount of images/OCP version 2. Run oc-mirror tool, have a file get created. 3.re-run oc-mirror tool using same imageset-config.yaml and see the mirror.tar file get over written.
Actual results:
mirror.tar file is overwritten on every run of oc-mirror tool
Expected results:
mirror.tar file should be named mirror$(date).tar or append the version of OpenShift being pulled in the imageset-config or place it in a uniquely named folder under content folder.
Additional info:
- is related to
-
CLID-428 Address feedback from NAPS Hackathon
-
- In Progress
-