[VROC] Error occurs during installation OS on degraded RAID volume

[Kinga Tanska]

Found on Ubuntu 22.04.1

Steps to reproduce:
1. Create RAID in preOS.
2. Disconnect RAID member to degrade volume.
3. Reboot.
4. Prepare install configuration file and set installation on GPT partition.
5. Start OS installation on degraded RAID volume using configuration file.
6. Wait for installation to finish.

Expected results:
OS should be installed successfully.
OS should boot from degraded RAID.

Actual results:
It's not possible to install OS on degraded RAID:

Running command ['mdadm', '--detail', '--scan', '-v'] with allowed return codes [0, 1] (capture=True)
        mdadm detail scan after assemble:
        ARRAY /dev/md/imsm0 level=container num-devices=3 metadata=imsm UUID=96c463f3:804edb63:c033cafe:cf718802
           devices=/dev/sda,/dev/sdf,/dev/sdg
        ARRAY /dev/md/r5d4s16_A_0 level=raid5 num-devices=4 container=/dev/md/imsm0 member=0 UUID=86eae79c:0fdb9874:7e3361e3:9bb16ea2
           devices=/dev/sda,/dev/sdf,/dev/sdg

        Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
        TIMED udevadm_settle(): 0.021
        RAID validation: name=/dev/md126 raidlevel=raid5 devices=[] spares=[] container=/dev/md127
        Running command ['mdadm', '--query', '--detail', '--export', '/dev/md126'] with allowed return codes [0] (capture=True)
        Verified /dev/md126 raid composition, raid is not OK
        Error checking raid /dev/md126: Array in degraded state: /dev/md126
        Error checking raid /dev/md126: Array in degraded state: /dev/md126
        An error occured handling 'volume': ValueError - Verified /dev/md126 raid composition, raid is not OK
        finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: configuring raid: volume
        TIMED BLOCK_META: 1.912
        finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command block-meta
        Traceback (most recent call last):
          File "/snap/subiquity/3698/lib/python3.8/site-packages/curtin/commands/main.py", line 202, in main
            ret = args.func(args)
          File "/snap/subiquity/3698/lib/python3.8/site-packages/curtin/log.py", line 97, in wrapper
            return log_time("TIMED %s: " % msg, func, *args, **kwargs)
          File "/snap/subiquity/3698/lib/python3.8/site-packages/curtin/log.py", line 79, in log_time
            return func(*args, **kwargs)
          File "/snap/subiquity/3698/lib/python3.8/site-packages/curtin/commands/block_meta.py", line 117, in block_meta
            return meta_custom(args)
          File "/snap/subiquity/3698/lib/python3.8/site-packages/curtin/commands/block_meta.py", line 2045, in meta_custom
            handler(command, storage_config_dict, command_handlers)
          File "/snap/subiquity/3698/lib/python3.8/site-packages/curtin/commands/block_meta.py", line 1626, in raid_handler
            raid_verify(
          File "/snap/subiquity/3698/lib/python3.8/site-packages/curtin/commands/block_meta.py", line 1582, in raid_verify
            verify_md_components(
          File "/snap/subiquity/3698/lib/python3.8/site-packages/curtin/commands/block_meta.py", line 1578, in verify_md_components
            raise ValueError(msg)
        ValueError: Verified /dev/md126 raid composition, raid is not OK
        Verified /dev/md126 raid composition, raid is not OK

[Michael Hudson-Doyle (mwhudson)]

I was thinking this was a duplicate of an old bug but that was a bit different https://bugs.launchpad.net/subiquity/+bug/1763647

I think so long as we make the status of the RAID clearly visible in the UI, the user should be able to install to a degraded array if they want to.

[Kinga Tanska (ktanska)]

Hello,

Thanks for information. If I understand correctly, this issue will be fixed, right?

[Kinga Tanska (ktanska)]

Due to closing our project in Intel, there is no reason to process it.
Please close this issue.