-
Bug
-
Resolution: Unresolved
-
Major
-
4.15.0
-
Important
-
None
-
2
-
CLID Sprint 247, CLID Sprint 248, CLID Sprint 253, CLID Sprint 254
-
4
-
Rejected
-
False
-
-
N/A
-
Release Note Not Required
-
Done
-
Customer Facing
Description of problem:
when use the oc-mirror with v2 format , will save the .oc-mirror dir to the default jjjjuser directory , and the data is very large. Now we don't have flag to specify the path for the log, but should save to the working directory.
Version-Release number of selected component (if applicable):
oc-mirror version WARNING: This version information is deprecated and will be replaced with the output from --short. Use --output=yaml|json to get the full version. Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.15.0-202312011230.p0.ge4022d0.assembly.stream-e4022d0", GitCommit:"e4022d08586406f3a0f92bab1d3ea6cb8856b4fa", GitTreeState:"clean", BuildDate:"2023-12-01T12:48:12Z", GoVersion:"go1.20.10 X:strictfipsruntime", Compiler:"gc", Platform:"linux/amd64"}
How reproducible:
always
Steps to Reproduce:
run command : oc-mirror --from file://out docker://localhost:5000/ocptest --v2 --config config.yaml
Actual results:
will save the logs to user directory.
Expected results:
Better to have flags to specify where to save the logs or use the working directory .
- clones
-
OCPBUGS-23309 oc-mirror should failed but not panic when falied to band port
- Closed
- is cloned by
-
OCPBUGS-24359 oc-mirror with v2 will create more data compared with v1 format
- Closed
- links to