Hi,

The necessary changes have been added to the "Director Installation ans Usage" guide.

Customers can view these changes on the Red Hat Customer Portal now. (The 
details are below.)

Thanks,
--Greg

   - The NOTE in step 8, here:
     -------------------------
     https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html-single/director_installation_and_usage/index#preparing-for-controller-replacement

   - The last step, here:
     --------------------
     https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html-single/director_installation_and_usage/index#cleaning-up-after-the-controller-node-replacement

Hi,

Removed step 7 in the "Director Installation and Usage" guide topic, "Preparing
for Controller replacement:"

   7. If you are using Open Virtual Switch (OVS) and replaced Controller nodes
      in the past without restarting the OVS agents, then restart the agents on
      the compute nodes before replacing this Controller. Restarting the OVS
      agents ensures that they have a full complement of RabbitMQ connections.

      Run the following command to restart the OVS agent:

      [heat-admin@overcloud-compute-0 ~]$ sudo docker restart neutron_ovs_agent

Removed step 11 in the "Director Installation and Usage" guide topic, "Cleaning
up after Controller node replacement:"

   11. If you are using Open Virtual Switch (OVS), and  the IP address for the
       Controller node has changed, then you must restart the OVS agent on all
       compute nodes:

       [heat-admin@overcloud-compute-0 ~]$ sudo podman restart neutron_ovs_agent

Customers can see these changes here:

   https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html-single/director_installation_and_usage/index#preparing-for-controller-replacement

--Greg