Skip to navigation

Bug Fix Advisory booty bug fix update

Advisory: RHBA-2011:0983-1
Type: Bug Fix Advisory
Severity: N/A
Issued on: 2011-07-21
Last updated on: 2011-07-21
Affected Products: Red Hat Enterprise Linux (v. 5 server)
Red Hat Enterprise Linux Desktop (v. 5 client)

Details

An updated booty package that fixes various bugs is now available for Red Hat
Enterprise Linux 5.

The booty package provides a small python library which is used to create boot
loader configuration files for the Anaconda and up2date utilities.

This updated package includes fixes for the following bugs:

* The Anaconda utility incorrectly installed GRUB (GRand Unified Bootloader) on
md RAID devices. According to the Anaconda's old setting, GRUB was installed to
look for a boot configuration on the hard disk it was running on. When RAID-1
(disk mirroring) was configured and the first hard drive failed, the system was
unable to continue the boot process. This could have happened because the second
hard drive became the new first hard drive but GRUB was still looking for the
second hard drive to boot from. This problem has been fixed and GRUB is now
installed correctly and refers to the right hard drive to boot from when one of
mirrors is lost. (BZ#213578)

* When a multipath device (mpath) name ended with a digit (for example:
rootpvp1), the Kickstart installation failed with a traceback report. This was
caused by an error in the mpath device name parser. This issue has been fixed
and a verification mechanism has been added to validate the mpath name. The
booty package now recognizes more mpath names and the installation fails with an
explanation if an invalid mpath name has been used. (BZ#572862)

* Prior this update, booty did not translate physical device names correctly for
md software RAID on dm devices (device-mapper subsystem devices), which caused
booty to crash during an installation. This issue has been fixed, physical
device names are translated correctly and booty no longer crashes in this case.
(BZ#667014)

All users of booty are advised to upgrade to this updated package, which
resolves these issues.


Solution

Before applying this update, make sure that all previously-released errata
relevant to your system have been applied.

This update is available via Red Hat Network. Details on how to use the Red Hat
Network to apply this update are available at
https://access.redhat.com/kb/docs/DOC-11259

Updated packages

Red Hat Enterprise Linux (v. 5 server)

SRPMS:
booty-0.80.6-10.src.rpm     MD5: 788f94fc006ed0bb42ae3c26c481155a
SHA-256: 31c4737e77aba63c89d39520064f0af9f49ece659795e508ae098879f6d179e5
 
IA-32:
booty-0.80.6-10.noarch.rpm     MD5: 53b439e9e6fe7b66d322a982b8be34d2
SHA-256: 3dd4fd5833ea88cb4a633aec1dd310a27304cdb4de770c5e4503ba3c15dc1e54
 
IA-64:
booty-0.80.6-10.noarch.rpm     MD5: 53b439e9e6fe7b66d322a982b8be34d2
SHA-256: 3dd4fd5833ea88cb4a633aec1dd310a27304cdb4de770c5e4503ba3c15dc1e54
 
PPC:
booty-0.80.6-10.noarch.rpm     MD5: 53b439e9e6fe7b66d322a982b8be34d2
SHA-256: 3dd4fd5833ea88cb4a633aec1dd310a27304cdb4de770c5e4503ba3c15dc1e54
 
s390x:
booty-0.80.6-10.noarch.rpm     MD5: 53b439e9e6fe7b66d322a982b8be34d2
SHA-256: 3dd4fd5833ea88cb4a633aec1dd310a27304cdb4de770c5e4503ba3c15dc1e54
 
x86_64:
booty-0.80.6-10.noarch.rpm     MD5: 53b439e9e6fe7b66d322a982b8be34d2
SHA-256: 3dd4fd5833ea88cb4a633aec1dd310a27304cdb4de770c5e4503ba3c15dc1e54
 
Red Hat Enterprise Linux Desktop (v. 5 client)

SRPMS:
booty-0.80.6-10.src.rpm     MD5: 788f94fc006ed0bb42ae3c26c481155a
SHA-256: 31c4737e77aba63c89d39520064f0af9f49ece659795e508ae098879f6d179e5
 
IA-32:
booty-0.80.6-10.noarch.rpm     MD5: 53b439e9e6fe7b66d322a982b8be34d2
SHA-256: 3dd4fd5833ea88cb4a633aec1dd310a27304cdb4de770c5e4503ba3c15dc1e54
 
x86_64:
booty-0.80.6-10.noarch.rpm     MD5: 53b439e9e6fe7b66d322a982b8be34d2
SHA-256: 3dd4fd5833ea88cb4a633aec1dd310a27304cdb4de770c5e4503ba3c15dc1e54
 
(The unlinked packages above are only available from the Red Hat Network)

Bugs fixed (see bugzilla for more information)

667014 - booty does not correctly translate physical device name for raids on dm devices



These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package

The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/