-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.21
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
x86_64
-
None
-
None
-
Proposed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
extraction the contents of the ZTP container includes a symbolic link that points to a target that does not exist in the container extra-manifest/workload/03-workload-partitioning.yaml -> ../../deprecated/workload/03-workload-partitioning.yaml
Version-Release number of selected component (if applicable):
This issue might exist in 4.20 container as well
skopeo --override-arch amd64 --override-os linux inspect --no-tags docker://registry.stage.redhat.io/openshift4/ztp-site-generate-rhel8:v4.21-2
{
"Name": "registry.stage.redhat.io/openshift4/ztp-site-generate-rhel8",
"Digest": "sha256:0b4983f9381584428a534b960ec6eb07dafedbff61b958e1dc3ad14cbca11136",
How reproducible:
Always
Steps to Reproduce:
1. extract source-crs and related files from container with a command similar to
mkdir -p output
podman run --rm --arch x86_64 --log-driver=none registry.stage.redhat.io/openshift4/ztp-site-generate-rhel8:"v4.21-2" extract /home/ztp --tar | \
tar x -C ./output
2. examine contents of output/
3.
Actual results:
link created that points to missing file
Expected results:
create the container including the target file instead of a symbolic link.
Additional info:
There may be other broken links in the container output. It would make sense to scrub the output tree for other broken links to avoid more bug reports.
- clones
-
OCPBUGS-65595 [siteconfig converter] ZTP container v4.21 tool fails with error
-
- Closed
-