Description of problem: The --skip-deploy-identifier flag does not have an effect when doing stack updates because all steps/deploy steps are executed again. There was an upstream change to fix (https://bugs.launchpad.net/tripleo/+bug/1860566) a problem with --skip-deploy-identifier in train. However it seems that the files /var/lib/tripleo-config/container-startup-config-step_{step}.json are not generated anymore but they were moved into /var/lib/tripleo-config/container-startup-config in corresponding step_{step} folders. [root@oc-ctl-1 ~]# cat /var/lib/tripleo-config/container-startup-config-readme.txt Container startup configs moved to /var/lib/tripleo-config/container-startup-config Version-Release number of selected component (if applicable): OSP 16.1 How reproducible: Steps to Reproduce: 1. Deploy an initial overcloud 2. Run a stack update without --skip-deploy-identifier and measure time 3. Run a stack update with --skip-deploy-identifier and measure time Actual results: Stack update with --skip-deploy-identifier takes the same amount of time as without because deploy tasks/steps are executed again Expected results: Stack update with --skip-deploy-identifier should take less time than without it because deploy tasks/steps should be skipped. Additional info:
Without --skip-deploy-identifier it took 27 minutes With --skip-deploy-identifier it took: real 17m20.163s user 0m6.950s sys 0m1.070s
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 (Red Hat OpenStack Platform 16.1.3 bug fix and enhancement 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-2020:5413