- Issued:
- 2007-11-15
- Updated:
- 2007-11-15
RHBA-2007:0816 - Bug Fix Advisory
Synopsis
anaconda bug fix and enhancement update
Type/Severity
Bug Fix Advisory
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated anaconda and anaconda-runtime packages that address several bugs
and add enhancements are now available.
Description
The anaconda package contains the program which was used to install your
system.
These updated packages fix the following bugs:
- the 2.6 series Linux kernel is limited to 15 SCSI partitions.
Installations on systems with more than 15 partitions resulted in numerous
errors such as the following:
Error informing the kernel about modifications to partition /dev/sdaX -
Invalid argument. This means Linux won't know about any changes you made to
/dev/sdaX until you reboot - so you shouldn't mount it or use it in any way
before rebooting. 96
(The 'X' in /dev/sdaX above is each partition above 15: for example 16, 17,
and so on).
After these errors a traceback occurred.
- removing an invalid RAID request from a kickstart file did not actually
remove the request; anaconda still tried to create the device.
- anaconda checked for conflicting labels before generating a new label. If
conflicting labels were found anaconda appended a "1", "2", and so on to
the extant label. This occurred when re-installing onto an already
partitioned and labeled disk. Disks are now labelled correctly.
- using the "--useexisting" option in a kickstart file for a RAID device
caused the following error: "couldn't get chunksize of md0: bad md magic on
device".
- anaconda crashed if "keep existing RAID partitions" was selected during
installation.
- during a Red Hat Enterprise Linux 4 installation, using an automatic
partitioning option while choosing to keep existing Logical Volume Manager
(LVM) partitions, resulted in the following error:
File "/usr/src/build/711711-ia64/install//usr/lib/anaconda/autopart.py",
line 1369, in doAutoPartition for d in r.drive: AttributeError:
RaidRequestSpec instance has no attribute 'drive'
This exception has been resolved in these updated packages.
- the kickstart post script on IBM System z architectures would fail with
numerous errors, including programs such as head, tail, and perl not being
found, and RPMs failing to install.
- retrieving a kickstart configuration file from a URL requiring
authentication failed.
- installing a Fully Virtualized Xen guest directly to a block device on
Red Hat Enterprise Linux 4 resulted in a "Error mounting file system on
hda1: No such device or address" pop-up window.
- network devices had to manually be specified when using the ksdevice boot
parameter.
- biosdisk installs would fail on certain hardware if each disk did not
have a unique disk signature.
- anaconda failed to correctly create LVM PVs of previously selected
drives during installation.
- anaconda failed to create unique disk labels on Itanium architectures. If
more than one Red Hat Enterprise Linux install was present, a "mount:
LABEL=/boot/efi duplicate - not mounted" error occurred during startup.
- on the IBM power 5 architecture, selecting "CD-ROM" as the installation
source failed, due to the CD-ROM not being found.
- the "diskboot.img" in the images directory of the first CD of "Red
Hat Enterprise Linux 4 Update 5 Work Station AMD/Intel 64" caused a
"Could not find kernel image: linux" error when booting a system.
This update also adds the following enhancements:
- disk size and model information is available during text-mode
installations.
- new "exclusivedisk" command allowing you to specify disks to use in
kickstart installations.
- documentation for the nfsmountopts and nicdelay command line arguments.
- OSA layer 2 network support for anaconda.
- support for the following hardware: NetXen and QLogic qla3xxx ethernet
adapters, and the ARECA SATA RAID host adapter.
- Intel EtherExpress/1000 gigabit driver to support the advanced
features found in Intel GbE devices.
- the CCISS driver is correctly labeled "HP/Compaq Smart Array Controller".
Users of the anaconda packages are advised to upgrade to these updated
packages, which resolve these issues and add these enhancements.
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
http://kbase.redhat.com/faq/FAQ_58_10188
Affected Products
- Red Hat Enterprise Linux Server 4 x86_64
- Red Hat Enterprise Linux Server 4 ia64
- Red Hat Enterprise Linux Server 4 i386
- Red Hat Enterprise Linux Workstation 4 x86_64
- Red Hat Enterprise Linux Workstation 4 ia64
- Red Hat Enterprise Linux Workstation 4 i386
- Red Hat Enterprise Linux Desktop 4 x86_64
- Red Hat Enterprise Linux Desktop 4 i386
- Red Hat Enterprise Linux for IBM z Systems 4 s390x
- Red Hat Enterprise Linux for IBM z Systems 4 s390
- Red Hat Enterprise Linux for Power, big endian 4 ppc
Fixes
- BZ - 172648 - anaconda crashes while trying to keep existing raid partition.
- BZ - 182943 - keeping existing partitions/LVM setup and autoconfigure without free OTHER free space causes exception
- BZ - 194247 - Can't get initial kickstart when URL requires auth
- BZ - 198526 - Interruptions to Kickstart
- BZ - 207541 - --useexisting can't find the existing RAID devices
- BZ - 207546 - ksdevice=link doesn't use nicdelay
- BZ - 209291 - kickstart install creates incorrect labels by appending a trailing "1"
- BZ - 233308 - anaconda doesn't remove all invalid RAID requests under kickstart
- BZ - 233639 - LTC33326: 200901: Update to installation tools - enable the netxen 10Gb Ethernet device as a network boot/install device
- BZ - 240561 - x86_64 diskboot.img no longer works
- BZ - 242113 - [Areca RHEL 4.6] Add anaconda/boot support for Areca RAID controllers (include arcmsr driver from 2.6.19)
- BZ - 247303 - BUG: biosdisk installs broken in some scenarios when unique disk signature dont exist
CVEs
(none)
References
(none)
Red Hat Enterprise Linux Server 4
SRPM | |
---|---|
anaconda-10.1.1.81-1.src.rpm | SHA-256: d876b8e920f9389b764239d4c92f5044eef1f61e0649115eabc0017e375470ae |
x86_64 | |
anaconda-10.1.1.81-1.x86_64.rpm | SHA-256: b25054eaaf414d58f72a00b8d48a7cc5f9c952101b531feeb46e5247c5300db3 |
anaconda-10.1.1.81-1.x86_64.rpm | SHA-256: b25054eaaf414d58f72a00b8d48a7cc5f9c952101b531feeb46e5247c5300db3 |
anaconda-runtime-10.1.1.81-1.x86_64.rpm | SHA-256: 4cc71cc61a027f2791813f71842e66eb5a77e1c9fcbe8e081b94cd00418f46e4 |
anaconda-runtime-10.1.1.81-1.x86_64.rpm | SHA-256: 4cc71cc61a027f2791813f71842e66eb5a77e1c9fcbe8e081b94cd00418f46e4 |
ia64 | |
anaconda-10.1.1.81-1.ia64.rpm | SHA-256: 5d7a7051ba1bae4f4b304aec83ec124b3b35f80a124139f5143a4b5c675d0982 |
anaconda-10.1.1.81-1.ia64.rpm | SHA-256: 5d7a7051ba1bae4f4b304aec83ec124b3b35f80a124139f5143a4b5c675d0982 |
anaconda-runtime-10.1.1.81-1.ia64.rpm | SHA-256: 792de4d9228339ccdd59c30204bc2e083f6cfe9d012070dceefb3c9c9bdd85d2 |
anaconda-runtime-10.1.1.81-1.ia64.rpm | SHA-256: 792de4d9228339ccdd59c30204bc2e083f6cfe9d012070dceefb3c9c9bdd85d2 |
i386 | |
anaconda-10.1.1.81-1.i386.rpm | SHA-256: 977dc4e4c008a20928e788183fdee3f55ac2f3a25c89a792181262f4056b7e21 |
anaconda-10.1.1.81-1.i386.rpm | SHA-256: 977dc4e4c008a20928e788183fdee3f55ac2f3a25c89a792181262f4056b7e21 |
anaconda-runtime-10.1.1.81-1.i386.rpm | SHA-256: ad9b439a4800e674d317accfb87c34eb9c03079d48ec047000b8a865eec3b083 |
anaconda-runtime-10.1.1.81-1.i386.rpm | SHA-256: ad9b439a4800e674d317accfb87c34eb9c03079d48ec047000b8a865eec3b083 |
Red Hat Enterprise Linux Workstation 4
SRPM | |
---|---|
anaconda-10.1.1.81-1.src.rpm | SHA-256: d876b8e920f9389b764239d4c92f5044eef1f61e0649115eabc0017e375470ae |
x86_64 | |
anaconda-10.1.1.81-1.x86_64.rpm | SHA-256: b25054eaaf414d58f72a00b8d48a7cc5f9c952101b531feeb46e5247c5300db3 |
anaconda-runtime-10.1.1.81-1.x86_64.rpm | SHA-256: 4cc71cc61a027f2791813f71842e66eb5a77e1c9fcbe8e081b94cd00418f46e4 |
ia64 | |
anaconda-10.1.1.81-1.ia64.rpm | SHA-256: 5d7a7051ba1bae4f4b304aec83ec124b3b35f80a124139f5143a4b5c675d0982 |
anaconda-runtime-10.1.1.81-1.ia64.rpm | SHA-256: 792de4d9228339ccdd59c30204bc2e083f6cfe9d012070dceefb3c9c9bdd85d2 |
i386 | |
anaconda-10.1.1.81-1.i386.rpm | SHA-256: 977dc4e4c008a20928e788183fdee3f55ac2f3a25c89a792181262f4056b7e21 |
anaconda-runtime-10.1.1.81-1.i386.rpm | SHA-256: ad9b439a4800e674d317accfb87c34eb9c03079d48ec047000b8a865eec3b083 |
Red Hat Enterprise Linux Desktop 4
SRPM | |
---|---|
anaconda-10.1.1.81-1.src.rpm | SHA-256: d876b8e920f9389b764239d4c92f5044eef1f61e0649115eabc0017e375470ae |
x86_64 | |
anaconda-10.1.1.81-1.x86_64.rpm | SHA-256: b25054eaaf414d58f72a00b8d48a7cc5f9c952101b531feeb46e5247c5300db3 |
anaconda-runtime-10.1.1.81-1.x86_64.rpm | SHA-256: 4cc71cc61a027f2791813f71842e66eb5a77e1c9fcbe8e081b94cd00418f46e4 |
i386 | |
anaconda-10.1.1.81-1.i386.rpm | SHA-256: 977dc4e4c008a20928e788183fdee3f55ac2f3a25c89a792181262f4056b7e21 |
anaconda-runtime-10.1.1.81-1.i386.rpm | SHA-256: ad9b439a4800e674d317accfb87c34eb9c03079d48ec047000b8a865eec3b083 |
Red Hat Enterprise Linux for IBM z Systems 4
SRPM | |
---|---|
anaconda-10.1.1.81-1.src.rpm | SHA-256: d876b8e920f9389b764239d4c92f5044eef1f61e0649115eabc0017e375470ae |
s390x | |
anaconda-10.1.1.81-1.s390x.rpm | SHA-256: 0bd8a4cb26d412261c2e12dcbc069e4e7f96ec487c28b5c4ab58bc1c5dfa1085 |
anaconda-runtime-10.1.1.81-1.s390x.rpm | SHA-256: e7eaa4f6e75bf1a5ac3545ed0144b55f58a7f97ad276616565183ae634fa9b1b |
s390 | |
anaconda-10.1.1.81-1.s390.rpm | SHA-256: 28efecb2caac3532679c2935ae036f64b478a6fe5c0d127ad1a8a10fe681bd66 |
anaconda-runtime-10.1.1.81-1.s390.rpm | SHA-256: 87c96121651230ee5801d5f5c26bd1b4cd5990871f1941cbe216cc74b74f7dc1 |
Red Hat Enterprise Linux for Power, big endian 4
SRPM | |
---|---|
anaconda-10.1.1.81-1.src.rpm | SHA-256: d876b8e920f9389b764239d4c92f5044eef1f61e0649115eabc0017e375470ae |
ppc | |
anaconda-10.1.1.81-1.ppc.rpm | SHA-256: dcb47d47d70b24f8f85ef9aa577e105c1058fc3347b0a181adb184b1c149d008 |
anaconda-runtime-10.1.1.81-1.ppc.rpm | SHA-256: 83ea213bc56e4eeaee858626f264ee3b6d46c4fabf5d3710f059b68415340334 |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.