Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 229574 - Anaconda bombs with a SIGSEGV when run with the noipv6 boot option
Summary: Anaconda bombs with a SIGSEGV when run with the noipv6 boot option
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: David Cantrell
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-21 21:15 UTC by Steve Salevan
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-03-06 21:04:54 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Steve Salevan 2007-02-21 21:15:42 UTC
Description of problem:
If a user attempts to disable IPv6 via attaching the 'noipv6' boot option,
anaconda tries to claim a dynamic IP without using IPv6.  However, halfway
through doing this, anaconda bombs with the following output:

loader received SIGSEGV!  Backtrace:
install exited abnormally [1/1]
sending termination signals...done
sending kill signals...done
disabling swap...
unmounting filesystems...
	/proc done
	/dev/pts done
	/sys done
	/tmp/ramfs done
you may safely reboot your system

Version-Release number of selected component (if applicable):
RHEL 5 Gold

How reproducible:
Always (at least when I try it)

Steps to Reproduce:
1. Start a RHEL 5 installation via CD or kickstart and ensure that the 'noipv6'
option is tagged onto the boot line.
2. Wait until Anaconda loads and watch it when it attempts to grab a dynamic IP
Actual results:
Anaconda bombs as above

Expected results:
Anaconda locates an IP within a reasonable amount of time and proceeds with the

Additional info:
This error was encountered on a VMware box and the RHEL 5 Gold installation was
initiated via an RHN Satellite-based kickstart.

Comment 1 David Cantrell 2007-03-06 21:04:54 UTC
I can't reproduce this with RHEL-5 GOLD on either real hardware or VMware.  DHCP
works fine when you pass the 'noipv6' argument at boot time.

Note You need to log in before you can comment on or make changes to this bug.