Bug 2143948

Description of problem:

At the moment there isn't an automated procedure to clean up the Pacemaker cluster resources configuration when InstanceHA is in place.
We need to have an automated procedure in place during the scale_down task to properly cleanup Pacemaker resources for the deleted Compute node.

Version-Release number of selected component (if applicable):

17.*

How reproducible:


Steps to Reproduce:
1. (undercloud) [stack@undercloud-0 ~]$ source ~/stackrc

2. (undercloud) [stack@undercloud-0 ~]$ vi /home/stack/composable_roles/network/baremetal_deployment.yaml

from:
~~~
...
- name: ComputeInstanceHA
  count: 2
  hostname_format: compute-%index%
  defaults:
    profile: compute
    network_config:
      template: /home/stack/composable_roles/network/nic-configs/compute.j2
    networks:
    - network: ctlplane
      vif: true
    - network: internal_api
    - network: tenant
    - network: storage
...
~~~

to:

~~~
...
- name: ComputeInstanceHA
  count: 1
  hostname_format: compute-%index%
  instances:
  - hostname: compute-0
    name: compute-0
  - hostname: compute-1
    name: compute-1
    provisioned: false
  defaults:
    profile: compute
    network_config:
      template: /home/stack/composable_roles/network/nic-configs/compute.j2
    networks:
    - network: ctlplane
      vif: true
    - network: internal_api
    - network: tenant
    - network: storage
...
~~~


3. (undercloud) [stack@undercloud-0 ~]$ openstack overcloud node delete --stack overcloud --baremetal-deployment /home/stack/composable_roles/network/baremetal_deployment.yaml


Actual results:

Deleted Compute node's resources are not automatically cleaned up in Pacemaker config. 


Expected results:

Deleted Compute node's resources are automatically cleaned up in Pacemaker config. 

Additional info: