Hide Forgot
Description of problem: Some images are available with tag 13.0, some with latest and some are missing (openstack-swift-container): (undercloud) [stack@osp13 ~]$ tag=`openstack overcloud container image tag discover \ > --image registry.access.redhat.com/rhosp13-beta/openstack-base:latest \ > --tag-from-label version` (undercloud) [stack@osp13 ~]$ echo $tag 13.0 (undercloud) [stack@osp13 ~]$ docker pull registry.access.redhat.com/rhosp13-beta/openstack-swift-container:13.0 Trying to pull repository registry.access.redhat.com/rhosp13-beta/openstack-swift-container ... error parsing HTTP 404 response body: invalid character 'F' looking for beginning of value: "File not found.\"" docker pull registry.access.redhat.com/rhosp13-beta/openstack-haproxy:13.0 Trying to pull repository registry.access.redhat.com/rhosp13-beta/openstack-haproxy ... error parsing HTTP 404 response body: invalid character 'F' looking for beginning of value: "File not found.\"" (undercloud) [stack@osp13 ~]$ docker pull registry.access.redhat.com/rhosp13-beta/openstack-haproxy:latest Trying to pull repository registry.access.redhat.com/rhosp13-beta/openstack-haproxy ... latest: Pulling from registry.access.redhat.com/rhosp13-beta/openstack-haproxy Digest: sha256:e4f20151ce35306701be80fd9f8648364d5f83c27b97c5a9c5438ec01af20d24 Status: Image is up to date for registry.access.redhat.com/rhosp13-beta/openstack-haproxy:latest Version-Release number of selected component (if applicable): OSP13 How reproducible: see above Steps to Reproduce: 1. 2. 3. Actual results: some images are not pulled Expected results: all images are pulled Additional info:
Issue identified with content push for containers for Beta. Correction being attempted currently.
# docker pull registry.access.redhat.com/rhosp13-beta/openstack-swift-container:13.0 Trying to pull repository registry.access.redhat.com/rhosp13-beta/openstack-swift-container ... 13.0: Pulling from registry.access.redhat.com/rhosp13-beta/openstack-swift-container Digest: sha256:7d9c4b996c5d1ecb788ab403342085696d9b3da88f4fc02d94cb697e5b74dfc3 Is now up and working. Also found 6 others that we are investigating Trying to pull repository registry.access.redhat.com/rhosp13-beta/openstack-barbican-keystone-listener ... unknown: Not Found Trying to pull repository registry.access.redhat.com/rhosp13-beta/openstack-barbician-api ... unknown: Not Found Trying to pull repository registry.access.redhat.com/rhosp13-beta/openstack-fluentd ... error parsing HTTP 404 response body: invalid character 'F' looking for beginning of value: "File not found.\"" Trying to pull repository registry.access.redhat.com/rhosp13-beta/openstack-zaqar ... error parsing HTTP 404 response body: invalid character 'F' looking for beginning of value: "File not found.\"" Trying to pull repository registry.access.redhat.com/rhosp13-beta/openstack-nova-scheduler ... error parsing HTTP 404 response body: invalid character 'F' looking for beginning of value: "File not found.\"" Trying to pull repository registry.access.redhat.com/rhosp13-beta/openstack-aodh-base ... error parsing HTTP 404 response body: invalid character 'F' looking for beginning of value: "File not found.\""
Verified all expected rhosp13-beta containers are up on redhat registry now.
*** Bug 1579483 has been marked as a duplicate of this bug. ***
*** Bug 1594110 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2085