Activity log for bug #1002357

Date Who What changed Old value New value Message
2012-05-21 15:44:41 Dimitri John Ledkov bug added bug
2012-05-21 23:43:28 Launchpad Janitor branch linked lp:~dmitrij.ledkov/ubuntu/quantal/mdadm/merge
2012-05-21 23:53:35 Dimitri John Ledkov mdadm (Ubuntu): status New In Progress
2012-05-21 23:53:53 Dimitri John Ledkov mdadm (Ubuntu): assignee Dmitrijs Ledkovs (dmitrij.ledkov)
2012-05-30 18:00:39 Launchpad Janitor mdadm (Ubuntu): status In Progress Fix Released
2012-06-22 20:02:36 Dimitri John Ledkov nominated for series Ubuntu Precise
2012-06-22 20:02:36 Dimitri John Ledkov bug task added mdadm (Ubuntu Precise)
2012-06-22 20:02:36 Dimitri John Ledkov nominated for series Ubuntu Quantal
2012-06-22 20:02:36 Dimitri John Ledkov bug task added mdadm (Ubuntu Quantal)
2012-06-22 20:02:43 Dimitri John Ledkov mdadm (Ubuntu Precise): status New Confirmed
2012-06-22 20:02:45 Dimitri John Ledkov mdadm (Ubuntu Precise): assignee Dmitrijs Ledkovs (dmitrij.ledkov)
2012-06-22 20:49:16 Dimitri John Ledkov mdadm (Ubuntu Precise): milestone ubuntu-12.04.1
2012-06-25 18:34:29 Dimitri John Ledkov mdadm (Ubuntu Precise): importance Undecided Medium
2012-06-26 08:55:42 Dimitri John Ledkov description # Sensible udev rules in debian $ find sid/debian/ -name '*.rules' | xargs -L 1 md5sum 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 # Crazy bit rotted 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 At the same time maybe a related udev.rules Bug #968074 can be fixed. [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] * 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 [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
2012-07-12 20:54:51 Stéphane Graber mdadm (Ubuntu Precise): status Confirmed Triaged
2012-07-16 09:30:21 Dimitri John Ledkov 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] * 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 [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 [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] * With previous release DDF or IMSM RAID arrays are not assembled * With new release they are assembled [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
2012-07-25 13:55:22 Stéphane Graber mdadm (Ubuntu Precise): status Triaged In Progress
2012-07-26 05:04:55 Steve Langasek mdadm (Ubuntu Precise): status In Progress Fix Committed
2012-07-26 05:04:59 Steve Langasek bug added subscriber Ubuntu Stable Release Updates Team
2012-07-26 05:05:01 Steve Langasek bug added subscriber SRU Verification
2012-07-26 05:05:03 Steve Langasek tags verification-needed
2012-07-27 09:04:06 Dimitri John Ledkov 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] * With previous release DDF or IMSM RAID arrays are not assembled * With new release they are assembled [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 [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) - external DDF - external ISMS * check that udev rules assemble all of above RAID arrays * expected results: - old udev rules assemble internal metadata only - new udev rules assemble all three [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
2012-08-11 06:26:02 Steve Langasek 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) - external DDF - external ISMS * check that udev rules assemble all of above RAID arrays * expected results: - old udev rules assemble internal metadata only - new udev rules assemble all three [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 [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
2012-08-13 17:42:25 Steve Langasek tags verification-needed verification-done
2012-08-13 19:43:09 Steve Langasek removed subscriber Ubuntu Stable Release Updates Team
2012-08-13 19:43:18 Launchpad Janitor mdadm (Ubuntu Precise): status Fix Committed Fix Released
2012-08-21 16:56:43 Launchpad Janitor branch linked lp:~ubuntu-branches/ubuntu/quantal/mdadm/quantal
2012-08-21 16:57:33 Launchpad Janitor branch linked lp:~ubuntu-branches/ubuntu/precise/mdadm/precise-proposed