90ed42da14
When we scale down a compute in an additional cell, disabling the compute
service fails in scale down tasks as the workflow of scale down a compute
from an additional cell is [1]:
- migrate off instances from the compute or delete them
- remove the compute from the cell (nova-manage command)
- scale down the cell stack
Until we have fully automated scale down of a compute from an additional
cell, don't run disable of compute service as we have already removed it from
cell in pre steps.
[1] https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/deploy_cellv2_manage_cell.html#delete-a-compute-from-a-cell
Change-Id: Ie699d7d3367652f4a4dfcb5bf7e52b81c4325aae
Closes-Bug: #1859825
(cherry picked from commit
|
||
---|---|---|
.. | ||
nova-api-container-puppet.yaml | ||
nova-az-config.yaml | ||
nova-base-puppet.yaml | ||
nova-compute-common-container-puppet.yaml | ||
nova-compute-container-puppet.yaml | ||
nova-conductor-container-puppet.yaml | ||
nova-ironic-container-puppet.yaml | ||
nova-libvirt-container-puppet.yaml | ||
nova-libvirt-guests-container-puppet.yaml | ||
nova-metadata-container-puppet.yaml | ||
nova-migration-target-container-puppet.yaml | ||
nova-scheduler-container-puppet.yaml | ||
nova-vnc-proxy-container-puppet.yaml | ||
novajoin-container-puppet.yaml |