To Reproduce Steps to reproduce the behaviour:

1. After the upgrade to 17.1 and respective reboot of controller nodes, Cu noticed an issue with octavia LBs. All of LBs are working, however, some of them are showing 'OFFLINE' in the list.
2. Checking health-manager pod, they noticed it is showing unhealthy and also logs are empty. No process is listening on port 5555. Last log entry is showing that hm is trying to attach to IP 172.24.3.166 (non-existent), but o-hm0 is configured with 172.24.2.77. The old (.166) IP cannot be found anywhere in the config.
3. if we compare the post-deploy configuration file with a previous successful upgrade case (04137133)  we can notice the IP addresses have been incorrectly updated after the upgrade.

Device Info (please complete the following information):

• [redhat-release] Red Hat Enterprise Linux release 9.2 (Plow)
• [rhosp-release] Red Hat OpenStack Platform release 17.1.6 (Wallaby)

Bug impact

• Currently LBs are working, serving production services. We have concern that while trying to fix health-manager, it could start failing over LBs.

Additional context

• sosreport on case 04170772
• template on case 04170772