Using latest tag to deploy containerized overcloud introduces an issue for updates. Need to differentiate between versions. Need to either have/document the tool to determine the tag or to document what tag to use for deployment.
Hi, If we're using latest we need https://github.com/openstack/python-tripleoclient/commit/eca5393ddcced5187b9d360a0b5edb96ca2a534e for update and we need to rework the update workflow. For reference, it should be noted that paunch without tag change (ie going to latest to latest) won't detect that the image is newer. So either we get date tag or we get latest and the prepare tag command and update the update workflow. The impact on upgrade need to be inspected as well.
The referenced commit is already in stable/pike, see https://review.openstack.org/#/c/506684/, it should be in latest puddle already.
This change will add the required label for "discover tag" to work with downstream images
Here is a proposed docs change describing "discover tag" https://gitlab.cee.redhat.com/sbaker/docs-Red_Hat_Enterprise_Linux_OpenStack_Platform/commit/568f0d0c5fbeab5c77fc13d9c8c43da5b14ae115
It's becoming a documentation issue, as the solution here is to run the discover-tag command instead of using --tag. in order to verify the Bug --> just need to check the documentation patch merged downstream
The docs change has landed: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12-beta/html/director_installation_and_usage/configuring-registry_details
Verified . discovered tag command is already in OSP12 Beta docs.
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:3457