| 2020-01-22 15:09:02 |
James Slagle |
description |
--skip-deploy-identifier when passed to openstack overcloud deploy is not working as intended because the wrong file is checked on the managed nodes for existence. Since the file is never found, the anisible task(s) are always assumed to have never run, thus they will always be run (or re-run).
Essentially, --skip-deloy-identifier has no effect due to checking for:
/var/lib/tripleo-config/container-startup-config-1.json
instead of:
/var/lib/tripleo-config/container-startup-config-step_1.json |
--skip-deploy-identifier when passed to openstack overcloud deploy is not working as intended because the wrong file is checked on the managed nodes for existence. Since the file is never found, the anisible task(s) are always assumed to have never run, thus they will always be run (or re-run).
Essentially, --skip-deloy-identifier has no effect due to checking for:
/var/lib/tripleo-config/container-startup-config-1.json
instead of:
/var/lib/tripleo-config/container-startup-config-step_1.json
Note this only affects train since the files were modified to be directories in master, and the check was fixed at that time as well. |
|
