-
Bug
-
Resolution: Done-Errata
-
Critical
-
rhos-17.1.4
-
None
-
1
-
False
-
-
False
-
No Docs Impact
-
openstack-neutron-18.6.1-17.1.20250307151001.85ff760.el9ost
-
None
-
-
-
Approved
-
Important
To Reproduce Steps to reproduce the behavior:
- Check the containers of ovn-metadata haproxy running in a compute node.
- Start a FFU from 16 to 17, run Compute node upgrade.
- Check that any containers was created.
- No error found.
Expected behavior
- Containers created and health or error log pointing the issue.
Device Info (please complete the following information):
- Hardware Specs: Total mem: 1547070 MB / Total CPU: 160
- OS Version: RHEL 9.2
- RHOSP: 17.1.4
Bug impact
- Customer is unable to use the updated computes.
Known workaround
- Downgrade to 17.1.3. Compute will work, but the agent will show as down in agent list.
Additional context
- Observed that some compute there were 2 images for openstack-neutron-metadata-agent-ovn. One at version 17.1.3 and another at version 17.1.4. It was tried to remove the image with 17.1.3 and restart the services tripleo_ovn_controller and tripleo_ovn_metadata_agent without success.
- blocks
-
OSPRH-13677 [QE] Run one or more of our jobs with power management enabled
-
- Closed
-
- is duplicated by
-
OSPRH-12903 BZ#2324141 ovn-metadata-agent not recovered after compute rebooted
-
- Closed
-
-
OSPRH-13504 restarting all compute nodes causes ovn-metadata-agent goes on unhealthy after 5 minutes of uptime
-
- Closed
-
- links to
-
RHBA-2025:3478 Red Hat OpenStack Platform 17.1.5 bug fix and enhancement advisory
(1 links to)