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 1685455

Summary: system upgrade from F29 to F30 stuck at the end of upgrade
Product: [Fedora] Fedora Reporter: Yann Droneaud <yann>
Component: dnf-plugins-extrasAssignee: Pavla Kratochvilova <pkratoch>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: dmach, extras-orphan, jkadlcik, jmracek, mblaha, pkratoch, rpm-software-management, vmukhame, yann
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-20 06:06:46 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 Flags
dnf system-upgrade download output (truncated)
none
system upgrade journal
none
dnf history info output none

Description Yann Droneaud 2019-03-05 09:28:20 UTC
Upgrading from F29 to F30 was stuck at the end of processing: eg. it doesn't automatically reboot at the end of the upgrade.

Upgrade was initiated with

    # dnf system-upgrade download --releasever=30 --best --allowerasing --skip-broken
    # dnf system-upgrade reboot

The system rebooted and started upgrading without noticeable errors.
Then it stopped with graphical message (in french):

    "Mise à niveau effectuée ! Nettoyage et redémarrage en cours ..."

(which translate to something like "Upgrade completed | Cleanup and reboot pending ...").

On the console, the messages were:

   "[ OK ] Started System Upgrade using DNF.
    [ OK ] Reached target Offline System Update.
    Mise à niveau effectuée ! Nettoyage et redémarrage en cours ..."

At this point I had to hit CTRL-ALT-DEL to initiate reboot (and then be greeted with a grub menu without any entries except memtest+, likely related to bug #1661955)

Comment 1 Yann Droneaud 2019-03-05 09:47:02 UTC
Created attachment 1540878 [details]
dnf system-upgrade download output (truncated)

(In reply to Yann Droneaud from comment #0)
> Upgrading from F29 to F30 was stuck at the end of processing: eg. it doesn't
> automatically reboot at the end of the upgrade.
> 
> Upgrade was initiated with
> 
>     # dnf system-upgrade download --releasever=30 --best --allowerasing
> --skip-broken

Here's the (truncated) output of the command. There was no error at the end, but the "typescript" file was truncated as the result of dnf system-upgrade reboot.

Comment 2 Yann Droneaud 2019-03-05 09:57:20 UTC
Created attachment 1540884 [details]
system upgrade journal

(In reply to Yann Droneaud from comment #0)
> 
> The system rebooted and started upgrading without noticeable errors.
> Then it stopped with graphical message (in french):
> 
>     "Mise à niveau effectuée ! Nettoyage et redémarrage en cours ..."
> 
> (which translate to something like "Upgrade completed | Cleanup and reboot
> pending ...").
> 
> On the console, the messages were:
> 
>    "[ OK ] Started System Upgrade using DNF.
>     [ OK ] Reached target Offline System Update.
>     Mise à niveau effectuée ! Nettoyage et redémarrage en cours ..."
> 
> At this point I had to hit CTRL-ALT-DEL to initiate reboot (and then be
> greeted with a grub menu without any entries except memtest+, likely related
> to bug #1661955)

Here the complete journal of the system upgrade, from boot to manual reboot.

Comment 3 Yann Droneaud 2019-03-05 09:59:44 UTC
Created attachment 1540888 [details]
dnf history info output

# dnf history list
ID     | Command line             | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
   437 | system-upgrade upgrade   | 2019-03-04 23:49 | D, E, I, O, U  | 5482 EE
...

# dnf history info 437
(see attached file)

Comment 4 Yann Droneaud 2019-03-05 10:03:48 UTC
Note: I have 3 DNF plugins enabled that alter DNF default behavior after install/upgrade/remove:
- python3-dnf-plugin-rpmconf
- python3-dnf-plugin-show-leaves
- python3-dnf-plugin-tracer

Maybe one of them is responsible for DNF system upgrade being stuck ?

Comment 5 Yann Droneaud 2019-03-05 10:04:36 UTC
(In reply to Yann Droneaud from comment #4)
> Note: I have 3 DNF plugins enabled that alter DNF default behavior after
> install/upgrade/remove:
> - python3-dnf-plugin-rpmconf
> - python3-dnf-plugin-show-leaves
> - python3-dnf-plugin-tracer
> 
> Maybe one of them is responsible for DNF system upgrade being stuck ?

It was the first time I attempted a system upgrade with those plugins installed.

Comment 6 Pavla Kratochvilova 2019-03-13 10:29:33 UTC
Hi,

First of all, thank you for all the logs, it's very helpful.

I wasn't able to reproduce this using the same commands and with the plugins installed, however, I noticed that in your case, there was a traceback during the upgrade. I guess that even though the transaction completed successfully, there were still some problems resulting from the skipped modular dependency problems (seen in the download output).

For the modular dependency problems, there was a patch that is not yet released. Can you please try to get the newest system-upgrade from our nightly repo and try the system upgrade with "--setopt=module_platform_id=f30" option? Steps to do so:
# dnf copr enable rpmsoftwaremanagement/dnf-nightly
# dnf upgrade dnf-plugin-system-upgrade
# dnf system-upgrade download --releasever=30 --setopt=module_platform_id=f30
# dnf system-upgrade reboot

The tracer plugin could also be a problem, so uninstalling it might help, too.

Comment 7 Pavla Kratochvilova 2019-03-20 06:06:46 UTC
The patch is now in Fedora 29, so you can ignore the first step. The option "--setopt=module_platform_id=f30" is still needed, though.

I am closing this bug as a duplicate, but if you can reproduce it with system-upgrade version 4.0.4 or higher, please don't hesitate to reopen the bug report.

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

Comment 8 Yann Droneaud 2019-04-02 15:02:06 UTC
(In reply to Pavla Kratochvilova from comment #7)

> The patch is now in Fedora 29, so you can ignore the first step. The option
> "--setopt=module_platform_id=f30" is still needed, though.
> 
> I am closing this bug as a duplicate, but if you can reproduce it with
> system-upgrade version 4.0.4 or higher, please don't hesitate to reopen the
> bug report.
> 
> *** This bug has been marked as a duplicate of bug 1656509 ***

In fact it's a common bug #1674045

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