When adding a new Compute node, the Availability Zone value of the existing Compute nodes will be changed in nova

Issue

• If a Compute node is added by overcloud deployment while the existing Compute node is registered in DeploymentServerBlacklist, the Availability Zone of the existing Compute node will be changed to nova.
• In the following example, the Availability Zone of the existing Compute nodes(compute-0 and compute-1) are changed from test to nova.

Example:

(overcloud) [stack@undercloud-0 ~]$ openstack compute service list
+--------------------------------------+----------------+---------------------------+----------+---------+-------+----------------------------+
| ID                                   | Binary         | Host                      | Zone     | Status  | State | Updated At                 |
+--------------------------------------+----------------+---------------------------+----------+---------+-------+----------------------------+
...
| e236d1a7-feea-46d7-84e4-bc73c50cc371 | nova-compute   | compute-1.redhat.local    | nova     | enabled | up    | 2022-06-15T02:27:18.000000 |  <===(*)
| cbbfcb0a-6fad-4ebd-95df-fddc339d2c5b | nova-compute   | compute-0.redhat.local    | nova     | enabled | up    | 2022-06-15T02:27:18.000000 |  <===(*)
| ab8b084f-8d94-4bc7-9469-a84cf773240d | nova-compute   | compute-2.redhat.local    | test     | enabled | up    | 2022-06-15T02:27:19.000000 |
+--------------------------------------+----------------+---------------------------+----------+---------+-------+----------------------------+