Bug 429947 - anaconda does not allow to correct network interface choices
anaconda does not allow to correct network interface choices
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Chris Lumens
Fedora Extras Quality Assurance
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2008-01-23 17:04 EST by Michal Jaegermann
Modified: 2008-04-02 14:41 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-02 14:41:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2008-01-23 17:04:38 EST
Description of problem:

While booting over a network a machine with two network interfaces,
and picking up an network method installation, like NFS, one arrives
eventually to "Configure TCP/IP" form.  So far so good but assume
that on a previous screen a "wrong" interface was chosen and
that we are using DHCP configuration (I can do here IPv4 only).

After a long timeout an attempt to configure fails, as expected,
and one can go "Back" one screen and pick up another interface.
This time a configuration attempt returns quickly and ...
we are starring back at "Configure TCP/IP".  There is no apparent
way forward.  An info on vt3 shows that at least DHCPOFFER
was received and on vt4 "eth1: links becomes ready".  No further

The only way out appears to be to restart the whole installation
procedere from scratch and choose another network interface this

Version-Release number of selected component (if applicable):
boot images dated 2008-01-22

How reproducible:
every time on few tries
Comment 1 Jeremy Katz 2008-01-29 11:45:01 EST
I think clumens made an attempt to fix this a day or two ago
Comment 2 Chris Lumens 2008-01-29 12:08:46 EST
Yes, this should be fixed in today's rawhide.
Comment 3 Michal Jaegermann 2008-03-29 18:42:29 EDT
Hm, I tried that with 20080329 images.  If that bug was fixed in January
then it is back.
Comment 4 Chris Lumens 2008-03-31 16:58:36 EDT
Here's the UI flow I'm seeing:

pick URL method -> pick wrong ethernet device -> configure tcp/ip -> wait wait
wait -> configure tcp/ip -> back -> pick right ethernet device -> configure
tcp/ip -> enter URL

Is this not the same flow that you are seeing?
Comment 5 Michal Jaegermann 2008-03-31 18:20:06 EDT
The flow I got, at least on Saturday, was like that:
pick wrong ethernet device -> try to configure tcp/ip via DHCP ->
wait wait wait -> back -> pick right ethernet device ->
try to configure tcp/ip via DHCP again -> quickly back to a dialog
screen with an interface configuration -> go into a configuration

After that reboot->pick up right ethernet device->configure->
get asked for URL.

I see that there are 20080331 images available.  Should I try that
again?  Downloading 100M+ of stage2.img is for me not so speedy
Comment 6 Michal Jaegermann 2008-04-02 14:41:37 EDT
I retried that with 20080402 images and now this behaves like expected,
i.e. like in comment #4.  Let us hope that it will stay that way
(although this is really not critical at all as rebooting in that moment
is still "cheap").

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