-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhos-18.0.15
-
None
-
0
-
False
-
-
False
-
?
-
rhos-ops-day1day2-edpm
-
None
-
-
-
-
Low
To Reproduce Steps to reproduce the behavior:
- Provision a NodeSet and a compute node.
- Scale in the NodeSet as described in the official docs: https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/maintaining_the_red_hat_openstack_services_on_openshift_deployment/assembly_scaling-data-plane-nodes#proc_removing-a-Compute-node-from-the-data-plane_scaling
- (optionally) Remove the BMH and associated secrets
- Create a new NodeSet
- Try to add the compute node to the new NodeSet (keeping the hostname)
- Run a OpenStackNodeSetDeployment
- The deployment of the node is stuck with the message{{ 'TLSInput error occured in TLS sources Object openstack/ovn-default-compute2 is already owned by another Ope nStackDataPlaneNodeSet controller openstack-data-plane'}}
Expected behavior
- The compute node is added to the new NodeSet and the deployment finishes successfully.
Device Info (please complete the following information):
- Tested on RHOSO 18.0.15
Bug impact
- Unable to "reprovision" nodes by migrating to different NodeSets in order to manage their configuration independently.
Known workaround
- Remove the CertificateRequests, Certificates and Secrets associated to the node after removing it from the original NodeSet.