Bug 212711 - Non-DHCP install causes anaconda exception
Non-DHCP install causes anaconda exception
Status: CLOSED DUPLICATE of bug 212018
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
6
All Linux
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-10-28 04:39 EDT by Jeff Garzik
Modified: 2013-07-02 22:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-10-29 21:25:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeff Garzik 2006-10-28 04:39:08 EDT
Description of problem:
Summary:  DHCP install works.  Non-DHCP install causes exception, when clicking
on the 'Fedora Extras' checkbox on the Repositories screen.

Machine:  ICH7 Intel SDV box.

Baseline:  FC6 x86-64 DVD install completes successfully, when using the default
(100% DHCP) network settings.

Problem case:  FC6 x86-64 DVD install crashes with a Python exception. 
Variation from baseline:  (a) entering a manual IPv4 address, netmask, primary
DNS server, and gateway.  IPv6 checkbox is unchecked, disabling IPv6.

Version-Release number of selected component (if applicable):
FC6 GA

How reproducible:
Always.

Steps to Reproduce:
1. Enter manual IPv4 address/netmask/gateway/DNS, rather than using DHCP.
2. Un-check the IPv6 checkbox, disabling IPv6.
3. Proceed through screens, until you reach the Repositories screen.
4. Check the Fedora Extras checkbox (which initiates the
activate-network-interface dialog).
  
Actual results:
Python exception, installer crash, kernel halt.

Expected results:
Installation proceeds, like it does with the all-DHCP install.
Comment 1 Chris Lumens 2006-10-29 21:25:22 EST

*** This bug has been marked as a duplicate of 212018 ***

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