Bug 1190415

Summary: fedup from updated 21 Workstation to Rawhide 2015-02-07 fails after upgrade-prep.sh
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: fedupAssignee: Will Woods <wwoods>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: bugzilla, danofsatx, robatino, tflink, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-12 16:39:50 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 Adam Williamson 2015-02-07 23:22:55 UTC
Tested fedup from a fully-updated F21 Workstation install to Rawhide nightly tree for 2015-02-07. The package download phase completed successfully and the 'System upgrade' boot menu option was created and bootable, but after it reaches the fedup target and completes upgrade-prep.sh, it fails:

upgrade-prep.sh[815]: upgrade prep complete, switching root...
systemd-coredump[876]: Failed to log coredump: Connection refused

and that's all she wrote, nothing more useful than that. I'll try and find a way to get better output later, wanted to log the issue for now.

Proposing as a Beta blocker, criterion "For each one of the release-blocking package sets, it must be possible to successfully complete an upgrade from a fully updated installation of the previous stable Fedora release with that package set installed. The user must be made to specify which Product (or none) they wish to have running when upgrade is complete." - https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria#Upgrade_requirements

Comment 1 Dan Mossor [danofsatx] 2015-02-09 18:00:56 UTC
Discussed at 02-09-2015 Blocker Review Meeting:
http://meetbot.fedoraproject.org/fedora-blocker-review/2015-02-09/fedora-blocker-review.2015-02-09-17.00.log.txt

AcceptedBlocker for Beta - This bug is a clear violation of the Beta upgrade requirements criterion: "For each one of the release-blocking package sets, it must be possible to successfully complete an upgrade from a fully updated installation of the previous stable Fedora release with that package set installed. The user must be made to specify which Product (or none) they wish to have running when upgrade is complete."

Comment 2 Chris Murphy 2015-02-09 18:35:08 UTC
This is likely a dupe of bug 1185604.

Comment 3 Adam Williamson 2015-02-12 16:39:50 UTC
yeah, I concur. Transferring accepted blocker status there. Sorry I missed it.

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