Red Hat Bugzilla – Bug 1500528
The output from "openstack overcloud container image prepare" should exclude mongodb.
Last modified: 2018-02-05 14:15:23 EST
The output from "openstack overcloud container image prepare" should exclude mongodb. Environment: openstack-tripleo-common-7.6.1-0.20170926174320.el7ost.noarch python-tripleoclient-7.3.1-0.20170925220840.f114a61.el7ost.noarch Currently running "openstack overcloud container image prepare" also generate a line with mongodb. This line shouldn't be there.
This affects deployments with local registry, as this step isn't needed for remote registry scenario.
The problem is that "openstack overcloud container image prepare" command with no arguments will create an entry for all the images that are defined in the /usr/share/openstack-tripleo-common/container-images/overcloud_containers.yaml.j2 template. You can filter the output of the prepare command to only the images that you're going to be using in the deployment by passing it the roles_data.yaml and the heat environment files that you're going to use in your deployment, respectively with the -r and -e options, similar to what you're using in your deploy command. Two things we should do: - remove the unused images from the default overcloud_containers.yaml file - include the docker.yaml and docker-ha.yaml files by default in the prepare command.
Since we don't build and support the mongodb image, I think we should carry a downstream patch to remove it from overcloud_containers.yaml.j2
tripleo-common patch for mongodb in build openstack-tripleo-common-7.6.3-0.20171010234827.el7ost
openstack-tripleo-common-7.6.3-2.el7ost built including patch for this please check and update status if this resolves it.
Verified: Environment: openstack-tripleo-common-7.6.3-3.el7ost.noarch The output from "openstack overcloud container image prepare" command doesn't include lines with mongodb now.
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-2017:3462