Bug 1054988

Summary:	F18->F19 upgrade doesn't start, missing "systemd.unit=..." (fedup-0.8.x)
Product:	[Fedora] Fedora	Reporter:	Will Woods <wwoods>
Component:	fedup	Assignee:	Will Woods <wwoods>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	lucas, tflink, wwoods
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-05 22:37:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Will Woods 2014-01-17 21:51:27 UTC

Upgrades to Fedora 19 using fedup-0.8.x don't start, they just boot into your normal system.

fedup-0.8.x doesn't add "upgrade systemd.unit=system-upgrade.target" to the boot args anymore. These arguments were removed because they caused a lot of other problems, like infinite reboot loops. (see bug 964303 and its many duplicates.)

This works as expected for upgrades to Fedora 20, but something goes wrong with upgrades to F19.


The simplest workaround for the moment is to add:

  upgrade systemd.unit=system-upgrade.target

to your boot arguments.

(If you have SELinux disabled, also add "selinux=0" - see bug 1044484)

Comment 1 Lucas 2014-01-21 15:04:18 UTC

This does not solve my problem. I entered those boot arguments and the same thing happens.

Also, I can't upgrade to 19 OR 20. I've tried both with the same results.

Yes I'm on fedup 0.8. Yes I've updated everything. I've tried removing all external disks.

what is going on here?

Comment 2 Will Woods 2014-01-21 18:22:14 UTC

(In reply to Lucas from comment #1)
> This does not solve my problem. I entered those boot arguments and the same
> thing happens.

Then you have a different problem. Without more information, I can't tell what's going on any more than an auto mechanic could tell you what's wrong from "my car doesn't start".

As the summary suggests, this bug covers *only* the case where:
- The upgrade doesn't start - it just boots your normal system, *and*
- you're trying to upgrade to Fedora 19 (or earlier), *and*
- you're using fedup-0.8.x.

If the system reboots immediately and doesn't upgrade, and you have fedora 0.7.x, that's bug 1044086.

If the system hangs and you have multiple LUKS partitions, that's bug 1045864.

If the system hangs and you are missing rd.luks.uuid/rd.lvm.vg boot args, that's bug 974000.

If the system just starts normally and doesn't upgrade, and you have a separate /var partition, that's bug 1045168.

Otherwise, please file a new bug, with a description of the actual behavior. Be sure to include the fedup version number, /etc/fstab, /var/log/fedup.log, the boot entry from /etc/grub*.conf, and the output of 'lsblk'.

Comment 3 Fedora End Of Life 2014-02-05 22:37:47 UTC

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.