Description of problem: The /var/lib/mistral/<overcloud stack name> directory is dropped when a scaledown is over. This prevent any debugging. It might be within tripleo-common or tripleoclient - not really sure about the component. Version-Release number of selected component (if applicable): openstack-tripleo-common-containers-11.3.2-0.20191127200418.5c82293.el8ost.noarch python3-tripleo-common-11.3.2-0.20191127200418.5c82293.el8ost.noarch openstack-tripleo-common-11.3.2-0.20191127200418.5c82293.el8ost.noarch python3-tripleoclient-12.3.1-0.20191202211445.46c5fb4.el8ost.noarch How reproducible: Always Steps to Reproduce: 1. Deploy Director + Overcloud 2. Remove an overcloud node (Compute for instance) 3. Check the existence of /var/lib/mistral/<overcloud stack name> Actual results: The directory is removed at some point Expected results: The directory should be there Additional info:
Removed a compute-1 from an overcloud with two computes: Before test: openstack server list +--------------------------------------+--------------+--------+------------------------+----------------+------------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+--------------+--------+------------------------+----------------+------------+ | 1b8ded0f-f016-4c0e-983b-08b76da31659 | controller-0 | ACTIVE | ctlplane=192.168.24.51 | overcloud-full | controller | | 10c1a230-5e00-4c98-80a7-87fafda40c0e | compute-0 | ACTIVE | ctlplane=192.168.24.26 | overcloud-full | compute | | d9be08b1-1b63-4ac0-89a5-75c705133f99 | compute-1 | ACTIVE | ctlplane=192.168.24.44 | overcloud-full | compute | +--------------------------------------+--------------+--------+------------------------+----------------+------------+ After compute-1 removed: openstack server list +--------------------------------------+--------------+--------+------------------------+----------------+------------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+--------------+--------+------------------------+----------------+------------+ | 1b8ded0f-f016-4c0e-983b-08b76da31659 | controller-0 | ACTIVE | ctlplane=192.168.24.51 | overcloud-full | controller | | 10c1a230-5e00-4c98-80a7-87fafda40c0e | compute-0 | ACTIVE | ctlplane=192.168.24.26 | overcloud-full | compute | +--------------------------------------+--------------+--------+------------------------+----------------+------------+ /var/lib/mistral/overcloud is still present after compute-1 removed: ls /var/lib/mistral/overcloud all_nodes_validation_script.sh deploy_steps_tasks_step_0.yaml hosts-config.sh ansible.cfg docker_puppet_script.yaml host_vars ansible-errors.json external_deploy_steps_tasks.yaml ObjectStorage ansible.log external_post_deploy_steps_tasks.yaml overcloud-config.tar.gz ansible.log-2020-02-07T17:06:48 external_update_steps_playbook.yaml post_update_steps_tasks.yaml ansible-playbook-command.sh external_update_steps_tasks.yaml post_upgrade_steps_playbook.yaml ansible-ssh external_upgrade_steps_playbook.yaml post_upgrade_steps_tasks.yaml BlockStorage external_upgrade_steps_tasks.yaml pre_upgrade_rolling_steps_playbook.yaml CephStorage fast_forward_upgrade_bootstrap_role_tasks.yaml pre_upgrade_rolling_steps_tasks.yaml common_deploy_steps_tasks_step_1.yaml fast_forward_upgrade_bootstrap_tasks.yaml scale_playbook.yaml common_deploy_steps_tasks.yaml fast_forward_upgrade_playbook.yaml scale_steps_tasks.yaml Compute fast_forward_upgrade_post_role_tasks.yaml ssh_private_key container_puppet_script.yaml fast_forward_upgrade_prep_role_tasks.yaml templates Controller fast_forward_upgrade_prep_tasks.yaml tripleo-ansible-inventory.yaml deploy-artifacts.sh fast_forward_upgrade_release_tasks.yaml update_steps_playbook.yaml deployments.yaml global_vars.yaml update_steps_tasks.yaml deploy_steps_playbook.yaml group_vars upgrade_steps_playbook.yaml
According to our records, this should be resolved by openstack-tripleo-common-11.3.3-0.20200121231250.3c68b48.el8ost. This build is available now.