Bug 520098

Summary: F12 alpha needs network during install
Product: [Fedora] Fedora Reporter: Joachim Backes <joachim.backes>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-28 19:57:13 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
none
yum.log
none
storage.log none

Description Joachim Backes 2009-08-28 12:09:30 UTC
Description of problem:
I installed F12 alpha from the DVD and had the impression that the
network (LAN) is used during installation. So the installation was
awfully slow.

For confirming this, I tried to install again after having
deactivated the LAN chip in the BIOS, and, indeeded, the
installation was cancelled by anaconda (after the install partition had been
formatted).


Version-Release number of selected component (if applicable):
F12 alpha

How reproducible:
each time

Steps to Reproduce:
1.Install F12 alpha without network access.
2.
3.
  
Actual results:
The installation process breaks after having formatted the HD partitions.

Expected results:
Installation possible without LAN access.

Additional info:

Comment 1 Chris Lumens 2009-08-28 13:36:03 UTC
Please attach whatever error message you are seeing here.  If it's an exception, attach the complete exception report.  If otherwise, please grab /tmp/anaconda.log, /tmp/storage.log, and /tmp/yum* and attach them to this report.  Thanks.

Comment 2 Joachim Backes 2009-08-28 15:32:31 UTC
Created attachment 359084 [details]
anaconda.log

Comment 3 Joachim Backes 2009-08-28 15:33:44 UTC
Created attachment 359085 [details]
yum.log

Comment 4 Joachim Backes 2009-08-28 15:34:18 UTC
Created attachment 359087 [details]
storage.log

Comment 5 Chris Lumens 2009-08-28 19:57:13 UTC
Oh, this is because udev isn't reporting an ID_FS_TYPE for any of your CD/DVD drives.  anaconda keys off that to know what filesystem is present.  Since there's nothing that reports an iso9660 filesystem, there's no apparent CDs/DVDs to install from.  Hence, we have to go to the network.  We already have a bug tracking this situation, so I'll dup it there.

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