ceph runtime config is updated incorrectly with new uuid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Ovidiu Poncea |
Bug Description
In a few areas in conductor/
1. if update requires a reboot but the new uuid does not come with reboot required bit, it will looks like the config is up to date, but system is not.
2. if update does not require a reboot but the new uuid comes with reboot require bit, the node becomes "config changed reboot required", until a reboot occurs.
code snippet looks like:
if utils.is_
else:
description: | updated |
description: | updated |
Changed in starlingx: | |
assignee: | nobody → Ovidiu Poncea (ovidiu.poncea) |
tags: |
added: stx.config removed: stx-config |
summary: |
- Update runtime config incorrectly with new uuid + ceph runtime config is updated incorrectly with new uuid |
tags: | added: stx.storage |
Marking as release gating; appears relate to the ceph upversion.
The impact is that the system configuration is not applied properly (silent failure).