Bug 1273390
Summary: | upgrade progress is not shown in Fedora 21 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||||||
Component: | dnf-plugin-system-upgrade | Assignee: | Will Woods <wwoods> | ||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 21 | CC: | awilliam, robatino, wwoods, zbyszek | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | Unspecified | ||||||||||||||
OS: | Unspecified | ||||||||||||||
Whiteboard: | RejectedBlocker | ||||||||||||||
Fixed In Version: | dnf-plugin-system-upgrade-0.5.0-1.fc21 | Doc Type: | Bug Fix | ||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2015-11-02 21:49:26 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: | |||||||||||||||
Attachments: |
|
Description
Kamil Páral
2015-10-20 10:59:37 UTC
Created attachment 1084680 [details]
no progress shown in graphics
Created attachment 1084681 [details]
no progress shown in text
Created attachment 1084682 [details]
workstation upgrade log
Created attachment 1084683 [details]
server upgrade log
Created attachment 1084684 [details]
minimal upgrade log
It seems our criteria cover only FN->FN+1 upgrade, but not FN-1->FN+1: "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. " https://fedoraproject.org/wiki/Fedora_23_Beta_Release_Criteria#Upgrade_requirements It seems to me they should, or our tools should not allow version skipping, but that's probably discussion for another time. But I think we should take into account that currently system-upgrade is almost completely broken (from user POV) for F21. Hardly anyone will wait 30+ minutes staring at "Starting system upgrade" message, without reading common bugs. It seems to me that we either need this fixed, or pull system-upgrade from F21 and continue using fedup. Please note that system-upgrade for F21 has been in updates-testing for more than a month, and apparently I was the first one to test it (or post feedback), today: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15941 Also, I asked dnf folks to push a libsolv fix for F21, which should fix bug 1260989: https://bodhi.fedoraproject.org/updates/FEDORA-2015-b3a8c0e68d However, this fix is quite risky from their POV, because the delta is quite large. To top it off, I didn't manage to reproduce bug 1260989 and I don't know why, so I'm not even sure it's needed and whether it's better to have it or not. A lot of uncertainty. We can still easily unpush system-upgrade from F21, fedup will not get obsoleted, libsolv fixes will not be needed, and people can use well-tested fedup for F21->F22 upgrade, and then use system-upgrade to go F22->F23. I tested F21->F22 upgrade using fedup and it works fine. I'm not sure a blocker discussion is the best channel to discuss this (since it might not fail our criteria), but since we don't have any other means to track things, marking as such. This should be fixed in dnf-plugin-system-upgrade 0.5.x (which is for F21 only), which a) switches the boot splash to text mode and b) dumps the DNF output to the console. See these two commits on f21-branch: https://github.com/rpm-software-management/dnf-plugin-system-upgrade/commit/e07cf7813c0cd623babb1b99ab044f8c075931b0 https://github.com/rpm-software-management/dnf-plugin-system-upgrade/commit/edbf7fe144fc953a3f67e4ca795e71582fd3803c A build of 0.5.x will come shortly after 0.7.x (which is the next F22+ version). Will, can you please make sure the new builds require latest dnf/hawkey/libsolv, as listed in bug 1260989? Because without those updates, system-upgrade will simply not work and fail with cryptic messages. Thanks! Discussed at 2015-10-22 Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-2/2015-10-22/f23-final-go_no_go-meeting.2015-10-22-16.00.log.txt . Rejected as a blocker: the criteria omission of upgrades from two releases before the one being tested is intentional, i.e., we specifically mean *not* to block on such upgrades. This may be revisited for future releases, but not for F23. (As the fix for this will be an update to F21, though, it will still get done, and probably before F23 release). dnf-plugin-system-upgrade-0.5.0-1.fc21 has been submitted as an update to Fedora 21. https://bodhi.fedoraproject.org/updates/FEDORA-2015-7627ff59ca dnf-plugin-system-upgrade-0.5.0-1.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update dnf-plugin-system-upgrade' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-7627ff59ca This is on its way to stable updates, so we probably don't need to document this on CommonBugs page (will be closed in a day). dnf-plugin-system-upgrade-0.5.0-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. |