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 1692617
Summary: | upgrading from 29 to 30 is incomplete: Upgrade seems to stop in cleaning process | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | tetsuji-rai | ||||||
Component: | dnf | Assignee: | Jaroslav Mracek <jmracek> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 30 | CC: | bugzilla, cheese, dmach, jmracek, jrohel, mblaha, mhatina, msuchy, packaging-team-maint, pkratoch, rpm-software-management, vmukhame | ||||||
Target Milestone: | --- | Keywords: | Triaged | ||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2019-04-01 16:31:27 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
tetsuji-rai
2019-03-26 03:23:04 UTC
I made a mistake in "Additional info". The fix to boot logo and shutdown screen anomaly, reinstall with "dnf -y reinstall \*". What f29 version of dnf is this? On the Fedora 29 system `rpm -q dnf` Can you attach a log of the failed upgrade? After rebooting from the failed attempt `sudo journalctl -b-1 -o short-monotonic > bug1692617_journaltxt` Is this a default installation of Fedora 29, or is the configuration custom somehow and can you describe it? If this is reproducible and you can post more information, please nominate it as a blocker bug, as failed upgrades violate the beta release criterion for upgrades. https://fedoraproject.org/wiki/Fedora_30_Beta_Release_Criteria#Upgrade_requirements Oh, I've already upgraded to fc30 and now these computers are up and running! No evidence of fc29 now!! So I try to install fc29 in unallocated space in my disk (fortunately I have a plenty of vacancy), and reproduce it. Moment please. I guess it will happen again. Ah, I forgot to mention upgrade itself didn't fail but was incomplete. Forced reboot (turn power off and on) boots f30. Boot screen and shutdown screen are still those of fc29 although using new kernel of fc30. But a lot of packages remained in the cache, so "dnf clean packages" must be run. After running "dnf -y reinstall \*", boot screen and shutdown screens went back to normal. Looks like post-scripts of some of fc30 packages hadn't run, because "Clean and reboot" procedure was interrupted. I tried it again by installing plain vanilla fc29 with C Development Tools and Libraries, Developing tools, System Tools, and RPMS Development Tools. I attached the screen photo during freezing. This screen showed for 45 mins, so I hit ctl+alt+del to reboot. Again the next boot screen was that of fc29. but running applications, configurations were of fc30. I made a mistake in previous messages: all the package scriptlets had run during cleaning. My systems are not customized, but the only difference is I use encrypted partition (lvm) for root,swap,home. Does that matter? And sorry for exaggeration of the title. Upgrade is successful, but incomplete. Not fails. dnf version of fc29 was dnf-4.2.2-1.fc29.noarch. Does that help? I'm going to upgrade this to rawhide. Created attachment 1550469 [details]
freezing screenshot
This lasted 45 mins, so I hit ctrl+alt+del to reboot. Then fc30 starts, but the boot screen was that of fc29.
Created attachment 1550472 [details] log during upgrading process result of "sudo journalctl -b-1 -o short-monotonic > bug1692617_journaltxt" Somehow finishing time in the first line is wrong. The problem seems at 3748.884010 sec, "Failed to get load state of reboot.target." This prevents reboot and causes freeze. Looks like a dup, if not reopen this bug by setting it to new. *** This bug has been marked as a duplicate of bug 1674045 *** |