Bug 954371
| Summary: | F19 Alpha fedup hangs after booting 'System Upgrade' | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stephen Gallagher <sgallagh> | ||||||||
| Component: | fedup | Assignee: | Will Woods <wwoods> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | awilliam, BobLfoot, loic.yhuel, robatino, tflink, wwoods | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | AcceptedBlocker | ||||||||||
| Fixed In Version: | fedup-0.7.3-5.fc17 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-05-15 03:31:06 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: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 834087, 957486 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Stephen Gallagher
2013-04-22 12:00:58 UTC
Created attachment 738481 [details]
Fedup log from Monday, April 22
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" [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 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 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". 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.
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. 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. 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). *** Bug 957486 has been marked as a duplicate of this bug. *** 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. 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. 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 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 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 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 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 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). Tested with GNome and KDE Desktop Test Cases fedup-0.7.3-4.fc18.noarch fixes this issue. 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). I also just tested an F18->F19 upgrade with current updates-testing fedup and it worked. Setting VERIFIED. 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 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. 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 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. 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. |