Bug 1500528 - The output from "openstack overcloud container image prepare" should exclude mongodb.
Summary: The output from "openstack overcloud container image prepare" should exclude ...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 12.0 (Pike)
Assignee: Steve Baker
QA Contact: Alexander Chuzhoy
Depends On: 1489801
TreeView+ depends on / blocked
Reported: 2017-10-10 20:41 UTC by Alexander Chuzhoy
Modified: 2023-02-22 23:02 UTC (History)
11 users (show)

Fixed In Version: openstack-tripleo-common-7.6.3-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 22:13:08 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Alexander Chuzhoy 2017-10-10 20:41:26 UTC
The output from "openstack overcloud container image prepare" should exclude mongodb.


Currently running "openstack overcloud container image prepare" also generate a line with mongodb. This line shouldn't be there.

Comment 1 Alexander Chuzhoy 2017-10-11 13:55:29 UTC
This affects deployments with local registry, as this step isn't needed for remote registry scenario.

Comment 2 Martin André 2017-10-11 14:23:25 UTC
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.

Comment 3 Steve Baker 2017-10-12 01:45:37 UTC
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

Comment 4 Jon Schlueter 2017-10-17 18:47:46 UTC
tripleo-common patch for mongodb in build  openstack-tripleo-common-7.6.3-0.20171010234827.el7ost

Comment 8 Jon Schlueter 2017-11-10 14:04:45 UTC
openstack-tripleo-common-7.6.3-2.el7ost built including patch for this please check and update status if this resolves it.

Comment 10 Alexander Chuzhoy 2017-11-16 15:31:48 UTC


The output from "openstack overcloud container image prepare" command doesn't include lines with mongodb now.

Comment 13 errata-xmlrpc 2017-12-13 22:13:08 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.