Bug 918894 - FedUp upgrade leaves system unbootable
Summary: FedUp upgrade leaves system unbootable
Keywords:
Status: CLOSED DUPLICATE of bug 964303
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-07 07:38 UTC by Raymond Mancy
Modified: 2014-12-08 01:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-09 19:28:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Raymond Mancy 2013-03-07 07:38:43 UTC
Description of problem:

Upgrade process from F17 -> F18 seems to leave the system unbootable.

Version-Release number of selected component (if applicable):
fedup-0.7.3-0.git20130128.fc17.noarch

How reproducible:
Always

Steps to Reproduce:
1.fedup --network 18
2. reboot system
3. system boots and succesfully installs a bunch of packages
4. reboot again, choose new 'Fedora (3.8.1-201.fc18.x86_64) menu entry


Actual results:
eventually it gives me "Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused" and hangs

Expected results:

not do that

Additional info:

I can see that the new menu entry still has some leftover kernel args from the 'System Upgrade" entry (which has since been removed/renamed), namely "upgrade systemd.unit=system-upgrade.target" (at least they look like a leftover). 

I tried removing these and it boots through to the gdm, but there are a host of further systemd errors printed to stdout, and after logging in nothing actually happens.

Comment 1 Raymond Mancy 2013-03-08 00:25:07 UTC
Ok so the udevd errors were in regard to hal packages that were left over. Even after removing them, the weirdness still happens with logging into the graphical.target

Comment 2 Will Woods 2013-10-09 19:28:51 UTC

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

Comment 3 Will Woods 2013-10-09 19:43:22 UTC
er, whoops - this is the right bug

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


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