Bug 698401

Summary: upgrade option requires network to be setup, fails to continue upgrade when canceling network setup
Product: [Fedora] Fedora Reporter: Jason Angus <jaduffa>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: anaconda-maint-list, dcantrell, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-02 13:30:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
anaconda.log as requested
none
syslog as requested
none
storage.log as requested
none
output of udevadm info --export-db none

Description Jason Angus 2011-04-20 19:53:07 UTC 
Description of problem:

When selecting to upgrade existing installation, setup (anaconda) asks for networking to be configured after selecting boot upgrade/replace option. Upgrade fails to continue after canceling network setup. eth0 only option given for network device to setup.

Version-Release number of selected component (if applicable):
f15 beta x86_64 dvd iso

How reproducible:
Tried upgrading from dvd iso three times, 'networking required' bug occurred for each of the three boot upgrade/replace options

Steps to Reproduce:
1. Select upgrade existing installation after booting from dvd 
2. Choose boot upgrade/replace option
3. You are then advised that networking is required for this installation

  
Actual results:
Upgrade fails to continue after canceling network setup

Expected results:


Additional info:
sounds like a repeat of the bug 677773 that was cleared with this beta release
Comment 1 Chris Lumens 2011-04-20 20:27:43 UTC 
Please attach /tmp/anaconda.log and /tmp/syslog to this bug report.
Comment 2 Jason Angus 2011-04-21 11:27:22 UTC 
Created attachment 493789 [details]
anaconda.log as requested

anaconda.log as requested
Comment 3 Jason Angus 2011-04-21 11:28:05 UTC 
Created attachment 493790 [details]
syslog as requested
Comment 4 Chris Lumens 2011-04-29 13:58:59 UTC 
I should have asked for /tmp/storage.log as well.  If you still have access to that (or at least to the output of udevadm info --export-db), that will prove my hypothesis right or wrong.

My guess is that your DVD drive has no ID_FS_TYPE in its udev entry, so anaconda does not know there's a DVD available for use.  Lacking that information, we fall back to the network as a source of packages.
Comment 5 Jason Angus 2011-04-30 01:24:47 UTC 
I've negelected to say that I transferred the DVD iso to a usb stick to use as install media.
Comment 6 Jason Angus 2011-04-30 01:25:20 UTC 
Created attachment 495897 [details]
storage.log as requested
Comment 7 Jason Angus 2011-04-30 01:26:50 UTC 
Created attachment 495898 [details]
output of udevadm info --export-db
Comment 8 Chris Lumens 2011-05-02 13:30:43 UTC 
anaconda does not attempt to discover installation sources on USB devices automatically - only CD/DVDs.  Since it's not finding one of those and you're not telling it where, it's falling back to HTTP.  You either need to add the askmethod or repo= parameters to the command line arguments.