defc4a8761
In order to install the bootloader on instances with software RAID, the IPA needs to chroot into the deployed image's root fs. Currently, the IPA assumes the first partition to contain the root fs, so this breaks with images where this is not the case. The proposed change extracts the root fs UUID from the image's metadata instead and passes it to the IPA (in the same way this is done for partition images). It keeps the current behaviour to send the UUID extracted from the driver internal info in case the metadata is not set on the image. For the time being, the IPA completely ignores the UUID passed anyway, so to make this fully work the IPA will also need to be patched. Change-Id: I69bd53aa24b7b10384dc1399a0acaa21d38d6bd9 Story: #2006649 Task: #37081
14 lines
563 B
YAML
14 lines
563 B
YAML
---
|
|
features:
|
|
- |
|
|
Software RAID is no longer limited to images which have the root file
|
|
system in the first partition.
|
|
upgrade:
|
|
- |
|
|
For Software RAID, the IPA no longer assumes that the root file system
|
|
of the deployed image is in the first partition. Instead, it will use
|
|
the UUID passed from the conductor. Operators need hence to make sure
|
|
that the conductor has the correct UUID (which either comes from the
|
|
'rootfs_uuid' field in the image metadata or from the
|
|
'root_uuid_or_disk_id' in the nodes 'internal_driver_info'.)
|