Bug 860533 - live installs over existing installation stalling at "Writing network configuration"
Summary: live installs over existing installation stalling at "Writing network configu...
Keywords:
Status: CLOSED DUPLICATE of bug 862801
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-26 05:01 UTC by Jens Petersen
Modified: 2012-10-16 11:30 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-10-16 11:30:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda log, taken at time of freeze (5.07 KB, text/plain)
2012-09-29 02:33 UTC, Eric Springer
no flags Details
ifcfg.log (844 bytes, text/plain)
2012-09-29 02:35 UTC, Eric Springer
no flags Details
packaging.log (164 bytes, text/plain)
2012-09-29 02:36 UTC, Eric Springer
no flags Details
program.log (180.28 KB, text/plain)
2012-09-29 02:36 UTC, Eric Springer
no flags Details
storage.log (233.25 KB, text/plain)
2012-09-29 02:37 UTC, Eric Springer
no flags Details

Description Jens Petersen 2012-09-26 05:01:30 UTC
Description of problem:
Live installs of F18 Alpha and later nightlies seem to stall for me
consistently at "Writing network configuration" when installing
over an existing Fedora installation.  Installing to a fresh disk
seems ok.  Rebooting into the unfinished install works!
(after waiting for anaconda disk activity to cease)

Version-Release number of selected component (if applicable):
anaconda-18.8

Steps to Reproduce:
1. install F18 Live over an existing Fedora install
  
Actual results:
Installer get stuck near end on progress screen showing
"Writing network configuration".

Expected results:
Install to finish normally.

Additional info:
Also happens with anaconda-18.9.

But does not happen for net install.

Comment 1 Chris Lumens 2012-09-26 18:55:37 UTC
What steps did you take that resulted in "installing over an existing Fedora installation"?

Comment 2 Jens Petersen 2012-09-28 09:53:47 UTC
I just mean as in doing an install rather than an upgrade say.

Currently it would be an old F18 install for me.
I can also test over an old F17 install if it helps.

Comment 3 Brian Lane 2012-09-28 15:45:21 UTC
Please attach the logs from /tmp/*log during the install to this bug as individual text/plain attachments.

Comment 4 Eric Springer 2012-09-29 02:33:06 UTC
Created attachment 618808 [details]
anaconda log, taken at time of freeze

Since I'm getting it too, here's my anaconda.log

Comment 5 Eric Springer 2012-09-29 02:35:35 UTC
Created attachment 618809 [details]
ifcfg.log

Comment 6 Eric Springer 2012-09-29 02:36:04 UTC
Created attachment 618810 [details]
packaging.log

Comment 7 Eric Springer 2012-09-29 02:36:35 UTC
Created attachment 618811 [details]
program.log

Comment 8 Eric Springer 2012-09-29 02:37:24 UTC
Created attachment 618812 [details]
storage.log

P.S. there really needs to be a way to upload multiple files at once :/

Comment 9 Jens Petersen 2012-10-05 04:01:53 UTC
This is might have been a duplicate or similar to bug 860791.

Comment 10 Mike FABIAN 2012-10-12 10:42:59 UTC
I believe I see the same problem when trying to install Fedora-18-Beta-TC3-x86_64-netinst.iso into qemu. 

The logs seem to be the same as those attached by Eric above.

Comment 11 Kamil Páral 2012-10-15 12:04:53 UTC
I think this could be a duplicate of bug 862801. Please retest with F18 Beta TC4, thanks.

Comment 12 Mike FABIAN 2012-10-16 08:41:32 UTC
Works for me with F18 Beta TC4. Thank you!

Comment 13 Kamil Páral 2012-10-16 11:30:02 UTC
Then I believe it really is a duplicate.

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


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