DIsabling nova on undercloud does not stop nova_compute container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
In Progress
|
High
|
Rabi Mishra |
Bug Description
When testing nova less deploy (i.e disabling nova on the undercloud by setting enable_nova=false in undercloud.conf after the first deploy with nova), nova-compute container is left behind running after undercloud install.
3cc1b8b39db0 undercloud.
and the wrapper systemd service (tripleo_
There is only one startup config left
[CentOS-8.2 - root@undercloud ~]# ls /var/lib/
mistral_
And it seems we've some logic in needs_delete filter not to clean orphaned containers when there is only one config or no config.
So, there seems to be 2 issues:
1. When there is 1 config for a step, orphaned containers are not cleaned.
2. When there is no config for a step (ex. when both nova and mistral are disabled and there is no startup config for step5), it seems contents of
/var/lib/
Changed in tripleo: | |
milestone: | none → victoria-3 |
Fix proposed to branch: master /review. opendev. org/748598
Review: https:/