-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
5
-
False
-
-
False
-
?
-
rhos-ops-day1day2-upgrades
-
None
-
-
-
-
RHOS Upgrades 2025 Sprint 17
-
1
-
Low
To Reproduce Steps to reproduce the behavior:
The logic in edpm-ansible uses 'bootc switch' return code to tell whether it should create a reboot-required flag: https://github.com/openstack-k8s-operators/edpm-ansible/blob/ab5197732ee36aec11b5ac99a16d1640d3b27e17/roles/edpm_update_system/tasks/bootc.yml#L18-L40
This is incorrect because 'bootc switch' will return 0 both on a successful switch, but also if there is nothing to do. Essentially the reboot flag will always get set regardless if we need to reboot or not.
Expected behavior
- Only set the reboot flag if reboot is needed (a bootc deployment is staged).
Bug impact
- Bootc deployments incorrectly signal that a reboot is needed when in fact it may not be needed.
Known workaround
- Instead of following the reboot-required flag, look at 'bootc status' and see if there is any deployment staged.
- blocks
-
OSPRH-15774 Updates with image mode dataplane nodes (dev workflow)
-
- Refinement
-
- links to