Use Debian-specific partx path in kpartx rule

debdiff for Bionic

debdiff for Focal

The attachment "lp2064201-multipath-tools-bionic.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

Thank you for the patches.

I uploaded the Focal changes after verifying that the bug is indeed present there. Bionic is in ESM now so I decided not to touch it; IIRC the changes will need to go through another process in this case.

Sorry, forgot to comment something else.

In the "Test Plan" section of the SRU text, could you please expand it a bit and also include an actual execution of the udev rule in question in order to confirm that the systemd-udev error doesn't happen anymore? It is generally not enough to just check if the new udev rule has the correct path for partx in it; we want to make sure that the execution of the rule doesn't generate any (new) errors.

Thanks.

Hello Chengen, or anyone else affected,

Accepted multipath-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/multipath-tools/0.8.3-1ubuntu2.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted multipath-tools (0.8.3-1ubuntu2.4) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

multipath-tools/unknown (s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#multipath-tools

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

@sergiodj Apologies for the oversight in not providing a detailed test plan earlier. I've now updated it. Thank you for your help.

I have followed the test plan and confirmed that the issue won't be occurred in 0.8.3-1ubuntu2.4.

root@focal:/# apt policy multipath-tools
multipath-tools:
  Installed: 0.8.3-1ubuntu2.4
  Candidate: 0.8.3-1ubuntu2.4
  Version table:
 *** 0.8.3-1ubuntu2.4 500
        500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     0.8.3-1ubuntu2.3 500
        500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
     0.8.3-1ubuntu2.1 500
        500 http://tw.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages
     0.8.3-1ubuntu2 500
        500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages