-
Bug
-
Resolution: Done
-
Critical
-
2.4.0.GA
Some old plugins in the CRW 2.4 registry are causing problems in the Z and P builds:
2020-08-28 12:15:34,034 - atomic_reactor.plugins.imagebuilder - INFO - [ERROR] Could not read image metadata through skopeo inspect --tls-verify=false; skip registry.redhat.io/codeready-workspaces/plugin-java11-openj9-rhel8:2.2 2020-08-28 12:15:34,035 - atomic_reactor.plugins.imagebuilder - INFO - [ERROR] Remove v3/plugins/redhat/java11/0.50.0/meta.yaml from registry. 2020-08-28 12:15:34,038 - atomic_reactor.plugins.imagebuilder - INFO - Reason: Registry registry.redhat.io/codeready-workspaces/plugin-java11-openj9-rhel8:2.2: 2020-08-28 12:15:34,039 - atomic_reactor.plugins.imagebuilder - INFO - time="2020-08-28T12:15:23Z" level=fatal msg="Error parsing image name \"docker://registry.redhat.io/codeready-workspaces/plugin-java11-openj9-rhel8:2.2\": error pinging docker registry registry.redhat.io: Get http://registry.redhat.io/v2/: dial tcp 104.113.9.148:80: connect: connection refused" 2020-08-28 12:15:34,039 - atomic_reactor.plugins.imagebuilder - INFO - Registry registry-proxy.engineering.redhat.com/rh-osbs/codeready-workspaces-plugin-java11-openj9-rhel8:2.2: 2020-08-28 12:15:34,040 - atomic_reactor.plugins.imagebuilder - INFO - time="2020-08-28T12:15:24Z" level=fatal msg="Error parsing image name \"docker://registry-proxy.engineering.redhat.com/rh-osbs/codeready-workspaces-plugin-java11-openj9-rhel8:2.2\": Error reading manifest 2.2 in registry-proxy.engineering.redhat.com/rh-osbs/codeready-workspaces-plugin-java11-openj9-rhel8: manifest unknown: manifest unknown" 2020-08-28 12:15:36,239 - atomic_reactor.plugins.imagebuilder - INFO - running 'if [[ ${USE_DIGESTS} == "true" ]]; then ./write_image_digests.sh v3; fi' failed with exit code 1
This currently blocks building any new plugin registry containers.
For now, I'm disabling z and p in the container.yaml: