+++ This bug was initially created as a clone of Bug #1585601 +++ Description of problem: Currently, there are 3 different images prepare command before any actual update is done to the overcloud, The commands are confusing and time-consuming. All the docker images and files preparation stage should be 1 single command/script. current prepare steps include: 1. Configure image file for the image upload ('openstack overcloud container image prepare' 2. Upload images listed in the file form previous command to the local registry (' openstack overcloud container image upload') 3. Create image file for heat stack from the step 1 file. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Running single command that will upload the images to local registry (optional) and will generate the update_param file used be heat stack Additional info:
This will happen in OSP-14 with the command "openstack tripleo container image prepare", but even running this will be optional because the prepare operations can happen during overcloud deploy.
This is likely best verified by seeing what infrared currently does, which should be zero or one calls to "openstack tripleo container image prepare" as per the upstream docs https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/container_image_prepare.html
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