Description of problem: openstack tripleo container image prepare default sets tag_from_label: rdo_version while it is expected to set it to tag_from_label: '{version}-{release}' Version-Release number of selected component (if applicable): python2-tripleo-common-9.1.1-0.20180710151736.8e8dabd.el7ost.noarch python-tripleoclient-heat-installer-10.2.1-0.20180709114814.e5ce9a8.el7ost.noarch python-tripleoclient-10.2.1-0.20180709114814.e5ce9a8.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Run openstack tripleo container image prepare default 2. Check resulting tag_from_label Actual results: tag_from_label: rdo_version Expected results: tag_from_label: '{version}-{release}' Additional info:
This is fixed as part of the change to switch to downstream puddles
[stack@undercloud-0 ~]$ openstack tripleo container image prepare default --local-push-destination # Generated with the following on 2018-10-09T12:33:05.933234 # # openstack tripleo container image prepare default --local-push-destination # parameter_defaults: ContainerImagePrepare: - push_destination: true set: ceph_image: rhceph-3-rhel7 ceph_namespace: registry.access.redhat.com/rhceph ceph_tag: latest name_prefix: openstack- name_suffix: '' namespace: registry.access.redhat.com/rhosp14 neutron_driver: null openshift_base_image: ose openshift_cockpit_image: registry-console openshift_cockpit_namespace: registry.access.redhat.com/openshift3 openshift_cockpit_tag: v3.9 openshift_etcd_image: etcd openshift_etcd_namespace: registry.access.redhat.com/rhel7 openshift_etcd_tag: latest openshift_gluster_block_image: rhgs-gluster-block-prov-rhel7 openshift_gluster_image: rhgs-server-rhel7 openshift_gluster_namespace: registry.access.redhat.com/rhgs3 openshift_gluster_tag: latest openshift_heketi_image: rhgs-volmanager-rhel7 openshift_heketi_namespace: registry.access.redhat.com/rhgs3 openshift_heketi_tag: latest openshift_namespace: registry.access.redhat.com/openshift3 openshift_tag: v3.9 tag: latest tag_from_label: '{version}-{release}'
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-2019:0045