[Bug 2031879] Re: Fail to remove a device via "mdadm -r" on ubuntu server 22.04.3

[shangsong]

Hi Julian,Jeff,
  I known this is a low priority issue and need more time to confirm it does not bring any other issue when  you revert it, but i think it is better to have fix schedule rather than endless waiting. 
Thus, could you setup a fix schedule for this issue?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/2031879

Title:
  Fail to remove a device via "mdadm -r" on ubuntu server 22.04.3

Status in mdadm package in Ubuntu:
  Fix Released
Status in mdadm source package in Jammy:
  Triaged
Status in mdadm source package in Lunar:
  Won't Fix
Status in mdadm source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * An explanation of the effects of the bug on users and

   * justification for backporting the fix to the stable release.

   * In addition, it is helpful, but not required, to include an
     explanation of how the upload fixes this bug.
    
  =>The customer will fail to remove NVME disk from container when they use "-r" option. if the fix can be backport into stable release , the users will remove successfully, no matter useing option '-r' or '--remove'.

  [ Test Plan ]
  To reproduce the issue:
  1. Fresh install Ubuntu server 22.04.3
  2. Create a container via below command:
  # mdadm -C /dev/md0 /dev/nvme0n1 /dev/nvme1n1 -n 2 -e imsm
  3. It will fail during removing a device from container /dev/md0
   # mdadm -r /dev/md0 /dev/nvme0n1
    mdadm: /dev/nvme0n1 does not appear to be an md device
   # mdadm /dev/md0 -r /dev/nvme0n1
    ==> No output

  It can pass via "mdadm --remove /dev/md0 /dev/nvme0n1"

  [ Where problems could occur ]

   * Think about what the upload changes in the software. Imagine the change is
     wrong or breaks something else: how would this show up?

   * It is assumed that any SRU candidate patch is well-tested before
     upload and has a low overall risk of regression, but it's important
     to make the effort to think about what ''could'' happen in the
     event of a regression.

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

   * This both shows the SRU team that the risks have been considered,
     and provides guidance to testers in regression-testing the SRU.

  [ Other Info ]

  This was fixed upstream with this commit:
  https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=190dc029b141c423e724566cbed5d5afbb10b05a

  We pulled this in earlier this year here:
  commit d1b153f83da24d9398a2c677d5bd962d622bf673 (tag: import/4.2+20230223-1)
  Author: Daniel Baumann <daniel.baumann at progress-linux.org>
  Date: Sat Feb 25 18:55:13 2023 +0100

      4.2+20230223-1 (patches unapplied)

      Imported using git-ubuntu import.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2031879/+subscriptions