-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.13
-
None
-
Moderate
-
No
-
3
-
OTA 233, OTA 234
-
2
-
Rejected
-
False
-
-
Description of problem:
Graph-data init container failed to run because of tar-entry metadata issue while trying to unpack the new graph-data tarball served on Production OSUS graph-data endpoint. # oc get pod NAME READY STATUS RESTARTS AGE sample-6694d466d-2sxpn 0/2 Init:CrashLoopBackOff 12 (3m53s ago) 40m updateservice-operator-5d5565cf5d-hktvw 1/1 Running 0 170m # oc logs sample-6694d466d-2sxpn graph-data ... blocked-edges/4.10.0-fc.0.yaml blocked-edges/4.1.10.yaml blocked-edges/4.1.1.yaml LICENSE tar: .: Cannot utime: Operation not permitted tar: .: Cannot change mode to rwxr-sr-x: Operation not permitted tar: Exiting with failure status due to previous errors
Version-Release number of selected component (if applicable):
How reproducible:
1/1
Steps to Reproduce:
1. Install OSUS operator 2. Build graph-data image using the Dockerfile FROM registry.access.redhat.com/ubi8/ubi:8.1 RUN curl -L -o cincinnati-graph-data.tar.gz https://api.openshift.com/api/upgrades_info/graph-data CMD exec /bin/bash -c "tar xvzf cincinnati-graph-data.tar.gz -C /var/lib/cincinnati/graph-data/" 3. Install update service instance
Actual results:
Tar-entry metadata issue is out while trying to unpack the new graph-data tarball
Expected results:
OSUS is installed successfully
Additional info:
- links to
(2 links to)