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 - upgrading from 29 to 30 is incomplete: Upgrade seems to stop in cleaning process
Summary: upgrading from 29 to 30 is incomplete: Upgrade seems to stop in cleaning process
Keywords:
Status: CLOSED DUPLICATE of bug 1674045
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 30
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jaroslav Mracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-26 03:23 UTC by tetsuji-rai
Modified: 2019-04-01 16:31 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-01 16:31:27 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
freezing screenshot (2.49 MB, image/jpeg)
2019-04-01 10:54 UTC, tetsuji-rai 		no flags Details
log during upgrading process (1.68 MB, text/plain)
2019-04-01 11:12 UTC, tetsuji-rai 		no flags Details
View All

Description tetsuji-rai 2019-03-26 03:23:04 UTC 
Description of problem:

During upgrading from fc29 to fc30, after the last "dnf system-upgrade reboot", the computer reboots and install packages, verifying, but the last "Clean and rebooting..." lasted more than an hour, so I hit "ctr+alt+del" to reboot manually.  Then it proceeded.

Version-Release number of selected component (if applicable):
only to fc30.

How reproducible:
Usually.   I tried 3 times on two machines and all failed.

Steps to Reproduce:
1.execute "dnf upgrade --refresh" in fc29.
2.execute "dnf install dnf-plugin-system-upgrade"
3.execute "dnf system-upgrade download --releasever=30"
4.and reboot with "dnf system-upgrade reboot"

Actual results:
Last clean and reboot process takes very long time. Almost no disk access.

Expected results:
Clean and reboot.

Additional info:
But it has a problem.  The upgraded system has a problem in the boot logo and shutdown screen.   In order to fix this, reinstall all packages again with "dnf -y upgrade" and it fixed all as far as I know in all three cases.

fc30 is still under development, so I just posted this for attention.
Comment 1 tetsuji-rai 2019-03-26 03:26:12 UTC 
I made a mistake in "Additional info".   The fix to boot logo and shutdown screen anomaly, reinstall with "dnf -y reinstall \*".
Comment 2 Chris Murphy 2019-04-01 05:58:41 UTC 
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
Comment 3 tetsuji-rai 2019-04-01 07:08:20 UTC 
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.
Comment 4 tetsuji-rai 2019-04-01 08:40:54 UTC 
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.
Comment 5 tetsuji-rai 2019-04-01 10:52:33 UTC 
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.
Comment 6 tetsuji-rai 2019-04-01 10:54:24 UTC 
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.
Comment 7 tetsuji-rai 2019-04-01 11:12:40 UTC 
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.
Comment 8 Chris Murphy 2019-04-01 16:31:27 UTC 
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 ***
Note You need to log in before you can comment on or make changes to this bug.