|Summary:||Traceback in stage2 when ipv6 only network device is activated in stage1.|
|Product:||Red Hat Enterprise Linux 6||Reporter:||Radek Vykydal <rvykydal>|
|Component:||anaconda||Assignee:||Radek Vykydal <rvykydal>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Release Test Team <release-test-team>|
|Fixed In Version:||anaconda-13.21.56-1||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-11-10 19:48:34 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Radek Vykydal 2010-06-18 13:55:17 UTC
Created attachment 425125 [details] The traceback. Description of problem: If a network device activated in stage 1 is missing ipv4 address, anaconda fails with traceback in stage 2. Version-Release number of selected component (if applicable): anaconda-13.21.50-1 How reproducible: Always Steps to Reproduce: 1. Install with stage2= boot parameter pointing to ipv6 address (e.g. stage2=http://[2001:aaaa::1]/install.img) 2. In stage 1, when asked to configure network device, uncheck "Enable IPV4 support". I used ipv6 predefined setting "Automatic Neigbor Discovery", having radvd on the link. 3. In stage 2, before network configuration screen there is the traceback. Actual results: Traceback attached. Expected results: No traceback. Additional info: This is issue also hit in https://bugzilla.redhat.com/show_bug.cgi?id=594090#c14. A patch is in anaconda-devel-list: https://www.redhat.com/archives/anaconda-devel-list/2010-June/msg00085.html waiting for review.
Comment 1 RHEL Product and Program Management 2010-06-18 14:03:26 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Comment 2 Radek Vykydal 2010-06-29 16:57:46 UTC
This should be fixed in anaconda-13.21.55-1.
Comment 5 email@example.com 2010-11-10 19:48:34 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.