The overcloud container image prepare command returned extra images which were not being built by downstream. If these were included, the containers would not be available.
The containers we don't generate were patched out of tripleo-common. Now all container images referenced by the overcloud container image prepare command are available as built images to be shipped in OSP 13.
After running openstack overcloud container image prepare --namespace docker-registry.engineering.redhat.com/rhosp13 --tag 2018-01-12.2 --prefix openstack- --set ceph_namespace=registry.access.redhat.com/rhceph --set ceph_image=rhceph-3-rhel7 --set ceph_tag=3-2 --output-images-file /home/stack/container_images.yaml
Some images from generated list are not available atm:
rhosp13/openstack-congress-api
rhosp13/openstack-mongodb
rhosp13/openstack-novajoin-notifier
rhosp13/openstack-novajoin-server
rhosp13/openstack-qdrouterd
rhosp13/openstack-skydive-agent
rhosp13/openstack-skydive-analyzer
(qdocker-registry.engineering replies for them with 'repository name not known to registry')
Verified OSP!3 RC - by running the prepare command according to osp13 documentation those containers mentioned in the BZ should not be part of the virt/docker-images.yaml and won't be downloaded or used in deployment.
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