The output from "openstack overcloud container image prepare" should exclude qdrouterd. 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 qdrouterd. This line shouldn't be there.
This affects deployments with local registry, as this step isn't needed for remote registry scenario.
See my comment [1] in bug #1500528. The images can be filtered out if you pass it your roles_data.yaml and heat environment files to the prepare command. I'm tempted to mark this bug as a duplicate of #1500528 since the issue will go away once we include the docker.yaml and docker-ha.yaml heat environment files by default in the prepare command. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1500528#c2
Since we don't build and support the qdrouterd image, I think we should carry a downstream patch to remove it from overcloud_containers.yaml.j2. I'll propose one fix for this and bug 1500528
tripleo-common patch for removing qdrouterd from j2 file merged in openstack-tripleo-common-7.6.3-0.20171010234827.el7ost
Environment: openstack-tripleo-common-7.6.3-0.20171010234828.el7ost.noarch (overcloud) [stack@undercloud-0 ~]$ openstack overcloud container image prepare --namespace=<namespace> --env-file=test1 1>/dev/null (overcloud) [stack@undercloud-0 ~]$ grep qdrouterd test1 (overcloud) [stack@undercloud-0 ~]$
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