Error messages from dnf update

What do these messages mean? They appear from time to time. Is it serious? Is any action required?

/var/cache/dnf/updates-7eea87b22825bc0d/packages/kernel-devel-5.15.14-200.fc35_5.15.15-200.fc35.x86_64.drpm: md5 mismatch of result
/var/cache/dnf/updates-7eea87b22825bc0d/packages/kernel-modules-5.15.14-200.fc35_5.15.15-200.fc35.x86_64.drpm: md5 mismatch of result
/var/cache/dnf/updates-7eea87b22825bc0d/packages/kernel-core-5.15.14-200.fc35_5.15.15-200.fc35.x86_64.drpm: md5 mismatch of result

Thank you

Attempting to restart after this update completed, froze the system necessitating a hard reset.

downloaded packages have checksum mismatch - most likely wrong (old) repository keys, Do you upgraded to 35 recently?

Close but not quite.

Each package as it is downloaded by dnf is verified to be intact by a checksum. If it fails the checksum dnf attempts to download that package again until it gets a successful clean downloaded package that matches the expected checksum.

What happens with the .drpm packages is that since the delta rpm failed to download cleanly dnf will download the full package instead of the delta. You should have seen that message following these you posted.

It is not an error, but simply a message that dnf is doing its job and ensuring it does not try to install packages that are corrupted during the download.

It would be nice if it reported that more explicitly, something like:
“Successfully downloaded full package after delta failed”

I get the sense that one goal of linux is to attract new users, many of whom will be novices. Fedora gets good marks from me but the more seamless it can be made should promote adoption.

I’ve been using various flavors of unix since the late 1980’s but it wasn’t until I tried Fedora that I went all in and decided to use it as my day-to-day system. Even Fedora, at times, devolves into a mind-reading exercise.

Thanks again

p.s. off topic. Since this web site uses cookies, why doesn’t it remember that you clicked “Fine”?

I just perused my logs from the last few weeks and I find this in the error logs for one recent kernel update, followed by the related dnf update log. The entries are separated since I keep the errors in a different file than the related successful actions, but you can see that they are reported as errors, like yours, then the package is successfully downloaded and installed.

/var/cache/dnf/updates-7eea87b22825bc0d/packages/kernel-modules-extra-5.15.12-200.fc35_5.15.13-200.fc35.x86_64.drpm: md5 mismatch of result
/var/cache/dnf/updates-7eea87b22825bc0d/packages/kernel-devel-5.15.12-200.fc35_5.15.13-200.fc35.x86_64.drpm: md5 mismatch of result
/var/cache/dnf/updates-7eea87b22825bc0d/packages/kernel-modules-5.15.12-200.fc35_5.15.13-200.fc35.x86_64.drpm: md5 mismatch of result
/var/cache/dnf/updates-7eea87b22825bc0d/packages/kernel-core-5.15.12-200.fc35_5.15.13-200.fc35.x86_64.drpm: md5 mismatch of result
 kernel                             x86_64 5.15.13-200.fc35 updates        15 k
 kernel-core                        x86_64 5.15.13-200.fc35 updates        35 M
 kernel-devel                       x86_64 5.15.13-200.fc35 updates        15 M
 kernel-modules                     x86_64 5.15.13-200.fc35 updates        33 M
 kernel-modules-extra               x86_64 5.15.13-200.fc35 updates       2.0 M
Packages to be upgraded above, download process below

(29/34): kernel-5.15.13-200.fc35.x86_64.rpm      91 kB/s |  15 kB     00:00    
[MIRROR] kernel-modules-extra-5.15.13-200.fc35.x86_64.rpm: Curl error (28): Timeout was reached for [SSL connection timeout]
[MIRROR] kernel-devel-5.15.13-200.fc35.x86_64.rpm: Curl error (28): Timeout was reached for [SSL connection timeout]
[MIRROR] kernel-modules-5.15.13-200.fc35.x86_64.rpm: Curl error (28): Timeout was reached for [SSL connection timeout]
dowload step completed, recovery of failed packages next

(1/4): kernel-modules-extra-5.15.13-200.fc35.x8  51 kB/s | 2.0 MB     00:39    
(2/4): kernel-devel-5.15.13-200.fc35.x86_64.rpm 130 kB/s |  15 MB     01:57    
(3/4): kernel-modules-5.15.13-200.fc35.x86_64.r 150 kB/s |  33 MB     03:41    
(4/4): kernel-core-5.15.13-200.fc35.x86_64.rpm  170 kB/s |  35 MB     03:30    
all packages now downloaded, installation below

  Installing       : kernel-core-5.15.13-200.fc35.x86_64                   2/69 
  Running scriptlet: kernel-core-5.15.13-200.fc35.x86_64                   2/69 
  Installing       : kernel-modules-5.15.13-200.fc35.x86_64                3/69 
  Running scriptlet: kernel-modules-5.15.13-200.fc35.x86_64                3/69 
  Installing       : kernel-5.15.13-200.fc35.x86_64                       31/69 
  Installing       : kernel-modules-extra-5.15.13-200.fc35.x86_64         32/69 
  Running scriptlet: kernel-modules-extra-5.15.13-200.fc35.x86_64         32/69 
  Installing       : kernel-devel-5.15.13-200.fc35.x86_64                 34/69 
  Running scriptlet: kernel-devel-5.15.13-200.fc35.x86_64                 34/69 
  Running scriptlet: kernel-core-5.15.13-200.fc35.x86_64                  69/69 
  Verifying        : kernel-5.15.13-200.fc35.x86_64                        1/69 
  Verifying        : kernel-core-5.15.13-200.fc35.x86_64                   2/69 
  Verifying        : kernel-devel-5.15.13-200.fc35.x86_64                  3/69 
  Verifying        : kernel-modules-5.15.13-200.fc35.x86_64                4/69 
  Verifying        : kernel-modules-extra-5.15.13-200.fc35.x86_64          5/69 

The fact that it later shows a successful download of that package followed by a successful install actually does tell you it succeeded without the overhead of detailing each recovery step.

If the download part of the update failed it would halt with the error at the end of the download and would not succeed in the transaction check and transaction test phase, before it actually began the update

Thanks. Your last comment about it halting on an onrecoverable error is new info for me and extremely helpful. Thanks for the detailed reply.