[Bug 1002357] Re: sort out udev rules madness (3 editions installed into 4 files)
Launchpad Bug Tracker
1002357 at bugs.launchpad.net
Mon Aug 13 19:43:18 UTC 2012
This bug was fixed in the package mdadm - 3.2.5-1ubuntu0.2
---------------
mdadm (3.2.5-1ubuntu0.2) precise-proposed; urgency=low
* Patch udev-md-raid.rules to not auto-start arrays based on detection
of ddf or isw (imsm) signatures; this conflicts with dmraid usage in
precise and requires more analysis before it can be enabled in SRU.
LP: #1030292.
mdadm (3.2.5-1ubuntu0.1) precise-proposed; urgency=low
* Stable Micro Point Bug Fix release:
- SRU master bug (LP: #1009973)
- Fixes segfault upon update-initramfs (LP: #969384)
- Fixes does not allow internal bitmap on version 1.2 arrays (LP: #1022915)
* Preserved previous behaviour, by reverting:
- bitmap chunk size of 0 will continue to mean 512B
- Modify the below fix, to accept previous syntax
"b10c663 config: fix handing of 'homehost' in AUTO line."
* Use upstream version of udev rules, instead of three slightly
different ubuntu udev rules (LP: #968074) (LP: #1002357)
* Add missing mdmon utility. This enables external metadata RAID
formats: DDF and Intel Matrix Storage Management (IMSM). (LP: #957494)
* Copy udev rule from /etc/udev/rules.d/ as well as the
/lib/udev/rules.d/, to allow local administrator to override mdadm
rules file (LP: #1017407)
* debian/initramfs/local-premount: add call wait_for_udev to wait a
little longer for RAID devices to appear. This improves
boot reliability. (LP: #942106)
mdadm (3.2.5-1) unstable; urgency=low
[ Michael Tokarev ]
* new upstream (bugfix) release, fixing regression when --add'ing
device to an array, introduced in 3.2.4, plus other minor fixes
(Closes: #673104, #673344)
* new patch: sha1-includes.diff to fix #include mess in new sha1.h
* added a check into debian/checkarray to skip checking arrays created
less than 2 weeks ago (Closes: #624273)
[ Dmitrijs Ledkovs ]
* Remove obsolete documentation dating back to ~etch release
* Remove reference to obsolete documention from debconf templates
* Update debconf templates translations
* Remove compatability with acient initramfs-tools
* Remove debian-specific mdadm-startall.8 in clean target
mdadm (3.2.4-1) unstable; urgency=low
* new upstream (bugfix) release (Closes: #664088, #661552)
* removed debian-run-udev.diff (applied upstream), and
all RUNDIR handling from debian/rules (it is the default now)
* add build-arch and build-indep targets to debian/rules, and
bump Standards-Version to 3.9.3
mdadm (3.2.3-3) unstable; urgency=low
* switch from topgit to plain 3.0 (quilt) layout, creating
debian/patches. Don't build-depend on quilt as patching
is done automatically by dpkg-source.
* debian/patches/debian-run-udev.diff by Roger Leigh (Closes: #644319, #627774)
* update debian/mdadm.logcheck.ignore.server to recognize "k" in
addition of "blocks" in kernel messages. Thanks to Frédéric Brière
for the patch (Closes: #656038)
-- Steve Langasek <steve.langasek at ubuntu.com> Fri, 03 Aug 2012 23:08:39 -0700
** Changed in: mdadm (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
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/1002357
Title:
sort out udev rules madness (3 editions installed into 4 files)
Status in “mdadm” package in Ubuntu:
Fix Released
Status in “mdadm” source package in Precise:
Fix Released
Status in “mdadm” source package in Quantal:
Fix Released
Bug description:
[IMPACT]
* Previously 3 different versions of udev rules where installed into
4 places (2 in the deb and 2 in the udeb)
* This causes confusion, as multiple mdadm rules are run. It is not
clear to the system administrator which udev rule to override in
/etc/. It is even more confusing for remastering udebs, as different
udev rule was needed to be overridden there.
* The solution is to use a single matching name udev rule in both deb
and udeb
* The upstream udev rule was chosen to be used as described in the
bug 968074
[TESTCASE #1]
* Unpack old deb and udeb into a temporary directory and execute a
command similar to this:
$ find quantal/ -name '*.rules' | xargs -L 1 md5sum
* Expected output is 4 files and 3 unique hashes
* Unpack new deb and udeb into a temporary directory and execute the
same command:
$ find precise-proposed/ -name '*.rules' | xargs -L 1 md5sum
* Expected output is 2 files with identical hashes
[TESTCASE #2]
* create RAID arrays with different metadata formats
- internal (0.9, 1.0, 1.1 or 1.2)
* check that udev rules assemble all of above RAID arrays
* expected results:
- both old and new udev rules assemble these arrays
[Regression Potential]
* Same as in the bug 968074, the default udev rule has changed.
Users who relied on the previous, incomplete/broken, udev rules may be
pleasantly surprised or annoyed that the udev rule name has changed to
match the one of Debian and upstream.
* System administrators need to check their /etc/udev/rules.d/ to
make sure that (a) they do not override mdadm rules (b) if they do,
check that those overrides are still needed (c) that the override is
named to match the new udev rule name.
[Other Info]
# Checksums and names of the old udev rules
$ find quantal/debian/ -name '*.rules' | xargs -L 1 md5sum
e143161798744026d7e4aac78e0bfede quantal/debian/mdadm/lib/udev/rules.d/65-mdadm-blkid.rules
916ce910a5829a0026a5b8bb3861c935 quantal/debian/mdadm/lib/udev/rules.d/85-mdadm.rules
6df86db16655769fa94086d3ee13453a quantal/debian/mdadm-udeb/lib/udev/rules.d/64-md-raid.rules
e143161798744026d7e4aac78e0bfede quantal/debian/mdadm-udeb/etc/udev/rules.d/65-mdadm-blkid.rules
$ Checksum, name and locations of the new udev rule
6df86db16655769fa94086d3ee13453a sid/debian/mdadm/lib/udev/rules.d/64-md-raid.rules
6df86db16655769fa94086d3ee13453a sid/debian/mdadm-udeb/lib/udev/rules.d/64-md-raid.rules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1002357/+subscriptions
More information about the foundations-bugs
mailing list