/etc/udev/rules.d/65-mdadm.vol_id.rules uses non-existent 'vol_id'

Bug #1127867 reported by Jamie Strandboge on 2013-02-17
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mdadm (Debian)
Fix Released
Unknown
mdadm (Ubuntu)
High
Dimitri John Ledkov
Lucid
Low
Unassigned
Oneiric
Low
Unassigned
Precise
High
Dimitri John Ledkov
Quantal
Low
Unassigned
Raring
High
Dimitri John Ledkov

Bug Description

[Impact]

 * In Lucid, /etc/udev/rules.d/65-mdadm.vol_id.rules conffile was dropped, but not properly removed in the preinst scripts. Later a conffile removal was added, but it had a wrong file name.

 * Causes errors to be printed on boot.

 * The fix is to properly remove this conffile.... all the until next LTS.

[Test Case]

 * Install mdadm package in Hardy, upgrade to precise, observe that the conffile is not removed.

 * Upgrading to raring/SRU'ed package should remove this conffile.

[Regression Potential]

 * Minimal as the conffile in question should not be used at boot.

[Original Description]

After upgrading a server from 10.04 to 12.04 I saw errors on boot about udev trying to use a non-existent vol_id:
failed to execute '/lib/udev/vol_id' 'vol_id --export /dev/md0': No such file or directory

I tracked this down to the following line in /etc/udev/rules.d/65-mdadm.vol_id.rules:
IMPORT{program}="vol_id --export $tempnode"

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541884 mentions this issue and says that we should be using '/sbin/blkid -o udev -p ...' instead. Indeed, checking /lib/udev/rules.d/64-md-raid.rules, it has:
IMPORT{program}="/sbin/blkid -o udev -p $tempnode"

I then updated /etc/udev/rules.d/65-mdadm.vol_id.rules to use this instead, and the errors went away.

Changed in mdadm (Ubuntu Precise):
importance: Undecided → High
Changed in mdadm (Ubuntu):
importance: Undecided → High
Changed in mdadm (Ubuntu Precise):
assignee: nobody → Dmitrijs Ledkovs (xnox)
Changed in mdadm (Ubuntu):
assignee: nobody → Dmitrijs Ledkovs (xnox)
Dimitri John Ledkov (xnox) wrote :

Hmm....
That rules file should not be present on precise and up since precise-release (as in the original 12.04.0) removes that conffile:
rm_conffile /etc/udev/rules.d/65_mdadm.vol_id.rules

Is that file still present on your system? it should have been removed on upgrade...

I haven't yet checked upgrading a 10.04 -> 12.04, and making sure the upgrade is correct. This is a next on todo.

Jamie Strandboge (jdstrand) wrote :

I still have this file. This was an upgrade from 10.04 to 12.04.

description: updated
Changed in mdadm (Ubuntu Quantal):
importance: Undecided → Low
Changed in mdadm (Ubuntu Oneiric):
importance: Undecided → Low
Changed in mdadm (Ubuntu Lucid):
importance: Undecided → Low
Dimitri John Ledkov (xnox) wrote :

I am suspecting your system may have a few other obsolete conffiles. My default test VM ended up having 14 obsolete conffiles. For this issue I have further filed bug 1160502 to hopefully address in the do-release-upgrader itself.

description: updated
Changed in mdadm (Ubuntu Lucid):
status: New → Confirmed
Changed in mdadm (Ubuntu Oneiric):
status: New → Confirmed
Changed in mdadm (Ubuntu Precise):
status: New → In Progress
Changed in mdadm (Ubuntu Quantal):
status: New → In Progress
Changed in mdadm (Ubuntu Raring):
status: New → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mdadm - 3.2.5-5ubuntu2

---------------
mdadm (3.2.5-5ubuntu2) raring; urgency=low

  * Remove the corr-ect unused conffile. (LP: #1127867)
 -- Dmitrijs Ledkovs <email address hidden> Tue, 26 Mar 2013 17:43:08 +0000

Changed in mdadm (Ubuntu Raring):
status: Fix Committed → Fix Released

Hello Jamie, or anyone else affected,

Accepted mdadm into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/mdadm/3.2.5-1ubuntu3.1 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 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

Changed in mdadm (Ubuntu Quantal):
status: In Progress → Fix Committed
tags: added: verification-needed
Changed in mdadm (Ubuntu Precise):
status: In Progress → Fix Committed
Dave Walker (davewalker) wrote :

Hello Jamie, or anyone else affected,

Accepted mdadm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/mdadm/3.2.5-1ubuntu0.3 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 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

The fix for this bug has been awaiting testing feedback in the -proposed repository for precise for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository.

tags: added: removal-candidate
Dimitri John Ledkov (xnox) wrote :

I have verified that /etc/udev/rules.d/65-mdadm.vol_id.rules is not present after installing mdadm in hardy and upgrading all the way to precise-proposed.

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mdadm - 3.2.5-1ubuntu0.3

---------------
mdadm (3.2.5-1ubuntu0.3) precise-proposed; urgency=low

  * Remove unused conffile. (LP: #1127867)
 -- Dmitrijs Ledkovs <email address hidden> Tue, 26 Mar 2013 17:43:08 +0000

Changed in mdadm (Ubuntu Precise):
status: Fix Committed → Fix Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mdadm - 3.2.5-1ubuntu3.1

---------------
mdadm (3.2.5-1ubuntu3.1) quantal-proposed; urgency=low

  * Remove unused conffile. (LP: #1127867)
 -- Dmitrijs Ledkovs <email address hidden> Tue, 26 Mar 2013 17:43:08 +0000

Changed in mdadm (Ubuntu Quantal):
status: Fix Committed → Fix Released
Rolf Leggewie (r0lf) wrote :

oneiric has seen the end of its life and is no longer receiving any updates. Marking the oneiric task for this ticket as "Won't Fix".

Changed in mdadm (Ubuntu Oneiric):
status: Confirmed → Won't Fix
tags: removed: removal-candidate
tags: added: precise
Changed in mdadm (Debian):
status: Unknown → Fix Released
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in mdadm (Ubuntu Lucid):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.