[Bug 2025563] Re: System can not shutdown if system has multiple VROC RAID arrays

[Athos Ribeiro]

Hi Cyrus, thanks for the patch!

As per the SRU guidelines in
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template, regarding
the "[ Where problems could occur ]" section,

>  * This must '''never''' be "None" or "Low", or entirely an argument as to why
   your upload is low risk.

Describing where problems could occur and how they would manifest is a
nice way to show to the SRU team that we did consider possible unwanted
outcomes for the SRU and that we'd be ready to address them in case they
do occur. It also helps people testing the SRU, guiding them on what to
look for when checking for regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2025563

Title:
  System can not shutdown if system has multiple VROC RAID arrays

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  The system can not shutdown if the system has multiple VROC RAID arrays.
  Intel has fixed it in systemd v251 [1]. 
  Need to cherry-pick the commit to ubuntu-jammy systemd 249.11-0ubuntu3.9.

  [1] The commit fixes the issue:
  commit 3a3b022d2cc112803ea7b9beea98bbcad110368a
  Author: Mariusz Tkaczyk <mariusz.tkaczyk at linux.intel.com>
  Date:   Tue Mar 29 12:49:54 2022 +0200

      shutdown: get only active md arrays.
      
      Current md_list_get() implementation filters all block devices, started from
      "md*". This is ambiguous because list could contain:
      - partitions created upon md device (mdXpY)
      - external metadata container- specific type of md array.
      
      For partitions there is no issue, because they aren't handle STOP_ARRAY
      ioctl sent later. It generates misleading errors only.
      
      Second case is more problematic because containers are not locked in kernel.
      They are stopped even if container member array is active. For that reason
      reboot or shutdown flow could be blocked because metadata manager cannot be
      restarted after switch root on shutdown.
      
      Add filters to remove partitions and containers from md_list. Partitions
      can be excluded by DEVTYPE. Containers are determined by MD_LEVEL
      property, we are excluding all with "container" value.
      
      Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk at linux.intel.com>

  
  [ Test Plan ]

  1. Build two VROC RAID. One RAID 0 for System volume, another RAID 10 for Data volume.
  2. Install system on System volume.
  3. Update systemd.
  4. Reboot the system.
  5. Verify if the system can reboot.

  [ Where problems could occur ]

  Low, upstream fix.

  [ Scope ]

  Jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2025563/+subscriptions