This is a clone of issue OCPBUGS-57786. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-57387. The following is the description of the original issue:
—
Description of problem:
Seeing “tainted” error now whilst running the following commands, one after the other, in the same dir. oc-mirror --v2 --config=imageset-config-save.yaml file://. oc-mirror --v2 --config imageset-config-save.yaml --from file://. docker://registry.example.com:8443/ocp4/openshift4
Version-Release number of selected component (if applicable):
4.18.0-202506021034
How reproducible:
Always
Steps to Reproduce:
1. In same dir, run: 2. oc-mirror --v2 --config=imageset-config-save.yaml file://. 3. oc-mirror --v2 --config imageset-config-save.yaml --from file://. docker://registry.example.com:8443/ocp4/openshift4
Actual results:
tar file is not unpacked and see the error: content filepath is tainted: working-dir/.history/.history-2025-06....
Expected results:
tar file should be unpacked and the images loaded into the registry.
Additional info:
Possibly, when I replace "." with $PWD it works ok, the tar file is unpacked.
- clones
-
OCPBUGS-57786 Seeing "content filepath is tainted" error when running d2m
-
- Closed
-
- is blocked by
-
OCPBUGS-57786 Seeing "content filepath is tainted" error when running d2m
-
- Closed
-
- links to
-
RHBA-2025:10767 OpenShift Container Platform 4.18.20 bug fix update