Bug 2344568 - continuous failure of dnf system-upgrade
Summary: continuous failure of dnf system-upgrade
Keywords:
Status: CLOSED DUPLICATE of bug 2242759
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 40
Hardware: aarch64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-09 17:42 UTC by R Bruce Hoffman
Modified: 2025-02-10 12:07 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 05:04:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description R Bruce Hoffman 2025-02-09 17:42:20 UTC
Multiple attempts at system-upgrade from 40 to 41 across the last month or two.
Looking at the messages, it appears that there is some problem with the GPG keys.
Deleted the GPG keys and re-executed, but no luck.

dnf log:

2025-01-09T00:01:28-0500 DEBUG Using rpmkeys executable at /usr/bin/rpmkeys to verify signatures
2025-01-09T00:05:16-0500 CRITICAL Problem opening package dnf5-5.2.8.1-3.fc41.aarch64.rpm
2025-01-09T00:05:16-0500 CRITICAL Problem opening package dnf5-plugins-5.2.8.1-3.fc41.aarch64.rpm
2025-01-09T00:05:16-0500 CRITICAL Problem opening package kernel-6.12.11-200.fc41.aarch64.rpm
2025-01-09T00:05:16-0500 CRITICAL Problem opening package kernel-core-6.12.11-200.fc41.aarch64.rpm
2025-01-09T00:05:16-0500 CRITICAL Problem opening package kernel-modules-6.12.11-200.fc41.aarch64.rpm
2025-01-09T00:05:16-0500 CRITICAL Problem opening package kernel-modules-core-6.12.11-200.fc41.aarch64.rpm
...
2025-01-09T00:05:16-0500 CRITICAL Problem opening package vim-enhanced-9.1.1081-1.fc41.aarch64.rpm
2025-01-09T00:05:16-0500 CRITICAL Problem opening package vim-filesystem-9.1.1081-1.fc41.noarch.rpm
2025-01-09T00:05:16-0500 CRITICAL Problem opening package vim-minimal-9.1.1081-1.fc41.aarch64.rpm
2025-01-09T00:05:16-0500 CRITICAL Problem opening package xxd-9.1.1081-1.fc41.aarch64.rpm
2025-01-09T00:05:16-0500 CRITICAL Problem opening package zlib-ng-compat-2.2.3-1.fc41.aarch64.rpm
2025-01-09T00:05:16-0500 DDEBUG Cleaning up.
2025-01-09T00:05:17-0500 DDEBUG Plugins were unloaded.
2025-01-09T00:05:17-0500 SUBDEBUG 
Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/dnf/cli/main.py", line 67, in main
    return _main(base, args, cli_class, option_parser_class)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dnf/cli/main.py", line 106, in _main
    return cli_run(cli, base)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dnf/cli/main.py", line 130, in cli_run
    ret = resolving(cli, base)
          ^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dnf/cli/main.py", line 183, in resolving
    base.do_transaction(display=displays)
  File "/usr/lib/python3.12/site-packages/dnf/cli/cli.py", line 248, in do_transaction
    self.gpgsigcheck(install_pkgs)
  File "/usr/lib/python3.12/site-packages/dnf/cli/cli.py", line 315, in gpgsigcheck
    raise dnf.exceptions.Error(_("GPG check FAILED"))
dnf.exceptions.Error: GPG check FAILED
2025-01-09T00:05:17-0500 CRITICAL Error: GPG check FAILED

Reproducible: Always

Steps to Reproduce:
1.dnf clean all
2.dnf system-upgrade download --releasever=41 -y
3.dnf system-upgrade reboot

(Removing GPG keys:  rpm -e `rpm -q -a | grep gpg-pubkey`
Actual Results:  
Boots back into 40 without any upgrade.

Expected Results:  
Boot into 41.

Comment 1 R Bruce Hoffman 2025-02-09 17:43:35 UTC
Keys most recently removed:

  171  rpm -e gpg-pubkey-a15b79cc-63d04c2c
  172  rpm -e gpg-pubkey-e99d6ad1-64d2612c
  173  rpm -e gpg-pubkey-d651ff2e-5dadbbc1
  174  rpm -e gpg-pubkey-94843c65-5dadbc64

Comment 2 amatej 2025-02-10 05:04:10 UTC
I think this is a problem with the system clock.
The issue is tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=2242759
(Please check it out for more details and workarounds.)

If it turns out this is a different problem please reopen.

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

Comment 3 R Bruce Hoffman 2025-02-10 12:07:42 UTC
The workaround of disabling/ending chronyd and enabling/activating systemd-timesyncd does allow the upgrade to run.


Note You need to log in before you can comment on or make changes to this bug.