-
Bug
-
Resolution: Done
-
Major
-
4.12
Description of problem:
sometimes the oc-mirror command will leave big data under /tmp dir and run out of disk space.
Version-Release number of selected component (if applicable):
oc mirror version
4.12/4.13
How reproducible:
Always
Steps to Reproduce:
1. Not sure the detail steps , but see logs when run oc-mirror command :
Actual results:
[root@preserve-fedora36 588]# oc-mirror --config config.yaml docker://yinzhou-133.mirror-registry.qe.gcp.devcluster.openshift.com:5000 --dest-skip-tls Checking push permissions for yinzhou-133.mirror-registry.qe.gcp.devcluster.openshift.com:5000 Creating directory: oc-mirror-workspace/src/publish Creating directory: oc-mirror-workspace/src/v2 Creating directory: oc-mirror-workspace/src/charts Creating directory: oc-mirror-workspace/src/release-signatures No metadata detected, creating new workspace The rendered catalog is invalid. Run "oc-mirror list operators --catalog CATALOG-NAME --package PACKAGE-NAME" for more information. error: error rendering new refs: render reference "registry.redhat.io/redhat/redhat-operator-index:v4.11": write /tmp/render-unpack-2866670795/tmp/cache/cache/red-hat-camel-k_latest_red-hat-camel-k-operator.v1.6.0.json: no space left on device [root@preserve-fedora36 588]# cd /tmp/ [root@preserve-fedora36 tmp]# ls imageset-catalog-registry-333402727 render-unpack-2230547823
Expected results:
Always delete the created datas under /tmp at any stations.
Additional info:
- clones
-
-
- Closed
-
- links to
