Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 954371 - F19 Alpha fedup hangs after booting 'System Upgrade'
Summary: F19 Alpha fedup hangs after booting 'System Upgrade'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
: 957486 (view as bug list)
Depends On:
Blocks: F19Beta, F19BetaBlocker 957486
TreeView+ depends on / blocked
 
Reported: 2013-04-22 12:00 UTC by Stephen Gallagher
Modified: 2013-06-23 05:57 UTC (History)
6 users (show)

Fixed In Version: fedup-0.7.3-5.fc17
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-15 03:31:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Fedup log from Friday, April 19 (940.10 KB, text/x-log)
2013-04-22 12:00 UTC, Stephen Gallagher 		no flags Details
Fedup log from Monday, April 22 (1.30 MB, text/plain)
2013-04-22 12:03 UTC, Stephen Gallagher 		no flags Details
Updated system-upgrade.target (429 bytes, text/plain)
2013-04-24 21:39 UTC, Will Woods 		no flags Details
View All

Description Stephen Gallagher 2013-04-22 12:00:58 UTC 
Created attachment 738478 [details]
Fedup log from Friday, April 19

Description of problem:
I ran 
sudo fedup --network 19 --instrepo=http://dl.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/

And it produced the attached log. When I rebooted into the upgrade kernel to perform the upgrade, it prompted me for my disk-encryption key, started to boot and then never completed. I reran it without the graphical display (so I could see the boot messages). It stalled partway through the bootup process (before package upgrading even began) with the following error:

systemd-cgroups-agent[594]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: connection refused

I also attempted to re-run fedup this morning, pulling in 370 newer package versions (the log of which I will attach separately). The same result occurred.


Version-Release number of selected component (if applicable):
fedup-0.7.3-1.fc18.noarch
systemd-197-1.fc18.2.x86_64

How reproducible:
Happened twice.

Steps to Reproduce:
1. Ran the fedup command above
2. Rebooted
3.
  
Actual results:
System stalled trying to boot to the upgrade mode

Expected results:
Upgrade should complete.

Additional info:
Comment 1 Stephen Gallagher 2013-04-22 12:03:21 UTC 
Created attachment 738481 [details]
Fedup log from Monday, April 22
Comment 2 Stephen Gallagher 2013-04-23 19:31:53 UTC 
Will requested the output of blkid:

/dev/sda1: LABEL="ssd256_boot" UUID="6d99bfa9-b81e-47bd-a62e-0a92baf2f7d0" TYPE="ext4"                                                                              
/dev/sda2: UUID="d6ac6d01-397e-4b7d-b715-9f98ccfe88d6" TYPE="crypto_LUKS"         
/dev/sda3: UUID="cGwzH5-M3LY-qK0z-p2an-uzIZ-TlR4-0TF3rJ" TYPE="LVM2_member"       
/dev/mapper/luks-d6ac6d01-397e-4b7d-b715-9f98ccfe88d6: UUID="JNGtQA-prP4-rG1T-UQV0-yIrF-8ePv-7piHzM" TYPE="LVM2_member" 
/dev/mapper/fedora_sgallagh520-swap: LABEL="ssd256_swap" UUID="abfafd6d-c3dc-4466-aa68-0c6559e87ad0" TYPE="swap" 
/dev/mapper/fedora_sgallagh520-root-real: LABEL="ssd256_root" UUID="be5180f2-5ac6-4625-9cc4-4ab38f8db146" TYPE="ext4" 
/dev/mapper/fedora_sgallagh520-root: LABEL="ssd256_root" UUID="be5180f2-5ac6-4625-9cc4-4ab38f8db146" TYPE="ext4" 
/dev/mapper/fedora_sgallagh520-upgradebackup-cow: TYPE="DM_snapshot_cow" 
/dev/mapper/fedora_sgallagh520-upgradebackup: LABEL="ssd256_root" UUID="be5180f2-5ac6-4625-9cc4-4ab38f8db146" TYPE="ext4" 
/dev/mapper/fedora_sgallagh520-home: UUID="ed38f98a-9b19-4f71-af45-4853bf02917e" TYPE="ext4"
Comment 3 Stephen Gallagher 2013-04-23 19:35:38 UTC 
[sgallagh@sgallagh520:~]$ sudo cat /proc/mounts
rootfs / rootfs rw 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
sysfs /sys sysfs rw,seclabel,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,seclabel,nosuid,size=1954528k,nr_inodes=488632,mode=755 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /dev/shm tmpfs rw,seclabel,nosuid,nodev 0 0
devpts /dev/pts devpts rw,seclabel,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,seclabel,nosuid,nodev,mode=755 0 0
tmpfs /sys/fs/cgroup tmpfs rw,seclabel,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
/dev/mapper/fedora_sgallagh520-root / ext4 rw,seclabel,noatime,nodiratime,discard,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,seclabel,relatime 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=34,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0
mqueue /dev/mqueue mqueue rw,seclabel,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
/dev/sda1 /boot ext4 rw,seclabel,noatime,nodiratime,discard,data=ordered 0 0
/dev/mapper/fedora_sgallagh520-home /home ext4 rw,seclabel,noatime,nodiratime,discard,data=ordered 0 0
Comment 4 Stephen Gallagher 2013-04-23 19:39:00 UTC 
Kernel boot command line:

Fedora 18 (working):
linux	/vmlinuz-3.8.8-202.fc18.x86_64 root=/dev/mapper/fedora_sgallagh520-root ro rd.md=0 rd.dm=0  rd.luks.uuid=luks-d6ac6d01-397e-4b7d-b715-9f98ccfe88d6 rd.lvm.lv=fedora_sgallagh520/root vconsole.keymap=us rd.lvm.lv=fedora_sgallagh520/swap rhgb quiet elevator=deadline LANG=en_US.UTF-8



Upgrade (not working):
linux	/vmlinuz-fedup root=/dev/mapper/fedora_sgallagh520-root ro rd.md=0 rd.dm=0  rd.luks.uuid=luks-d6ac6d01-397e-4b7d-b715-9f98ccfe88d6 rd.lvm.lv=fedora_sgallagh520/root vconsole.keymap=us rd.lvm.lv=fedora_sgallagh520/swap rhgb quiet elevator=deadline LANG=en_US.UTF-8 upgrade systemd.unit=system-upgrade.target plymouth.splash=fedup enforcing=0
Comment 5 Stephen Gallagher 2013-04-23 19:41:58 UTC 
Also, it's worth noting that the state it gets stuck in does not respond to ctrl-alt-del, and sysrq-t produces no output except "Displaying system state".
Comment 6 Will Woods 2013-04-24 21:39:27 UTC 
Created attachment 739607 [details]
Updated system-upgrade.target

The fact that C-A-D fails is significant - it shows that we're stuck in very early systemd startup stuff.

Try replacing the existing /usr/lib/systemd/system/system-upgrade.target with this file and let me know if that lets the upgrade start.

You might want to add 'rd.upgrade.test' to the boot arguments - this will make it skip the actual upgrade, which lets you test to see if there are problems other than the RPM upgrade transaction itself.
Comment 7 Loïc Yhuel 2013-04-24 23:02:29 UTC 
I had the same problem and your system-upgrade.target allowed to do the upgrade.

NOTE : the upgrade was done with fedup-0.7.3-1.fc18 (installed from koji to check if it wasn't the source of the problem), not with fedup-0.7.1-1.fc18 which is the only version in f18 repos.
Comment 8 Stephen Gallagher 2013-04-25 12:42:53 UTC 
Confirmed, with this patch I can run through the test upgrade mostly successfully. The RPM upgrade tests completed with only non-fatal issues, but when it got to the shutdown phase, I got an error message "systemd-cryptsetup[PID]: Failed to deactivate: Device or resource busy".

I'm not sure if that's related or not. Anyway, I'm off to try performing an actual upgrade now. Thank you for the quick turnaround on this.
Comment 9 Stephen Gallagher 2013-04-25 13:45:06 UTC 
I was able to complete an upgrade to Fedora 19 alpha with this patch applied. The real upgrade also hit the issue where it did not reboot at the end (leaving me in a state where I needed to perform a forcible power off to restart it).
Comment 10 Will Woods 2013-04-29 13:50:44 UTC 
*** Bug 957486 has been marked as a duplicate of this bug. ***
Comment 11 Will Woods 2013-04-29 14:27:54 UTC 
Tracking the reboot problem as bug 957783; this bug concerns the failure to *start* the upgrade, which should be fixed in fedup-0.7.3-3.
Comment 12 Robert Lightfoot 2013-04-29 17:02:29 UTC 
fedup-0.7.3-3 works to produce a useable system with minimal install and with gnome install on both i386 and x86_64 archs as tested past day by me.  As 0.7.3-3 is not yet in Bodhi I cannot add karma.  Please note bug 957783 is present in fedup-0.7.3-3.
Comment 13 Fedora Update System 2013-04-30 14:52:38 UTC 
fedup-0.7.3-3.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/fedup-0.7.3-3.fc18
Comment 14 Fedora Update System 2013-04-30 14:56:31 UTC 
fedup-0.7.3-3.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/fedup-0.7.3-3.fc17
Comment 15 Fedora Update System 2013-04-30 15:39:07 UTC 
fedup-0.7.3-4.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc17
Comment 16 Fedora Update System 2013-04-30 15:39:36 UTC 
fedup-0.7.3-4.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc18
Comment 17 Fedora Update System 2013-04-30 15:40:37 UTC 
fedup-0.7.3-4.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/fedup-0.7.3-4.fc19
Comment 18 Fedora Update System 2013-04-30 20:10:17 UTC 
Package fedup-0.7.3-4.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fedup-0.7.3-4.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-7092/fedup-0.7.3-4.fc19
then log in and leave karma (feedback).
Comment 19 Robert Lightfoot 2013-05-01 05:31:52 UTC 
Tested with GNome and KDE Desktop Test Cases fedup-0.7.3-4.fc18.noarch fixes this issue.
Comment 20 Adam Williamson 2013-05-01 16:51:03 UTC 
Discussed at 2013-05-01 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-01/f19beta-blocker-review-2.2013-05-01-16.01.log.txt . Accepted as a blocker (with a side note that this needs to be fixed in F18, not F19, and so does not block F19 composes).
Comment 21 Adam Williamson 2013-05-07 00:52:33 UTC 
I also just tested an F18->F19 upgrade with current updates-testing fedup and it worked. Setting VERIFIED.
Comment 22 Robert Lightfoot 2013-05-07 09:05:21 UTC 
Please note that fedup-0.7.3-4.fc17 is busted for F17 to F18 upgrade.  And fedup-0.7.3-4.fc19 when installed on a fresh Beta-TC3 System will not go from F19 -> rawhide or F19 -> F20
Comment 23 Fedora Update System 2013-05-15 03:31:06 UTC 
fedup-0.7.3-4.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 24 Fedora Update System 2013-06-07 16:44:17 UTC 
fedup-0.7.3-5.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/fedup-0.7.3-5.fc17
Comment 25 Fedora Update System 2013-06-08 03:35:29 UTC 
fedup-0.7.3-4.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 26 Fedora Update System 2013-06-23 05:57:33 UTC 
fedup-0.7.3-5.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.