9f1c1ccce6
When https://review.opendev.org/c/openstack/python-tripleoclient/+/775302 merged, it changed the function signature of utils.archive_deploy_artifacts, but the tripleo deploy code was not updated to pass the right arguments. This caused the templates directory to be considered the working directory and the artifact tarball was generated in that directory, and then promptly deleted during the cleanup phase. This patch updates tripleo deploy to pass the right arguments to archive_deploy_artifacts, and also use a consistent working directory based on the stack name under ~/tripleo-deploy instead of defaulting to the home dir. This is a cleaner approach than just leaving all the files in the home dir, especially given that tripleo deploy can deploy multiple stacks, and if the same directory was used as the default, there would be file collisions. Closes-Bug: #1921975 Signed-off-by: James Slagle <jslagle@redhat.com> Change-Id: Idded7faba1ff6c811b94503c559029aeeaca6a06
9 lines
390 B
YAML
9 lines
390 B
YAML
---
|
|
features:
|
|
- The "openstack tripleo deploy" and "openstack undercloud install" commands
|
|
now save their generated artifacts from the deployment under a single
|
|
consistent directory, which by default is located at
|
|
~/tripleo-deploy/<stack>. For the undercloud, this location is
|
|
~/tripleo-deploy/undercloud. The directory can be overridden with the
|
|
--output-dir option.
|