fedora-iot

#50 layered kernel-modules-extra constantly blocks rpm-ostree upgrade
Closed: working as intended by pbrobinson. Opened by stenwt.

Closed: working as intended
Reopen Issue

I hit this issue roughly 9 times out of 10 when attempting to upgrade via rpm-ostree upgrade. It also is currently blocking rpm-ostree deploy of 36.20221005.0 on one system, even though another system with kernel-modules-extra was able to upgrade to that release a week ago.

This is super confusing and annoying, I would appreciate some help understanding why this breaks so often and what I can do to avoid it. I do rely on modules from kernel-modules-extra. 

[root@hpt4 ~]# sudo rpm-ostree upgrade
note: automatic updates (stage) are enabled
⠈ Receiving objects; 98% (6250/6336) 7.0 MB/s 211.5 MB
Receiving objects; 98% (6250/6336) 7.0 MB/s 211.5 MB... done
Checking out tree 4da3ef7... done
Enabled rpm-md repositories: updates fedora rancher-k3s-common-stable fedora-cisco-openh264
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
Updating metadata for 'rancher-k3s-common-stable'... done
Updating metadata for 'fedora-cisco-openh264'... done
Importing rpm-md... done
rpm-md repo 'updates'; generated: 2022-10-14T12:46:13Z solvables: 24921
rpm-md repo 'fedora'; generated: 2022-05-04T21:16:11Z solvables: 67992
rpm-md repo 'rancher-k3s-common-stable'; generated: 2022-08-16T00:42:54Z solvables: 7
rpm-md repo 'fedora-cisco-openh264'; generated: 2022-10-06T11:02:51Z solvables: 4
Resolving dependencies... done
error: Could not depsolve transaction; 1 problem detected:
 Problem: conflicting requests
  - package kernel-modules-extra-5.19.15-201.fc36.x86_64 requires kernel-uname-r = 5.19.15-201.fc36.x86_64, but none of the providers can be installed
  - package kernel-modules-extra-5.17.5-300.fc36.x86_64 requires kernel-uname-r = 5.17.5-300.fc36.x86_64, but none of the providers can be installed
  - cannot install both kernel-core-5.19.15-201.fc36.x86_64 and kernel-core-5.19.14-200.fc36.x86_64
  - cannot install both kernel-core-5.17.5-300.fc36.x86_64 and kernel-core-5.19.14-200.fc36.x86_64

It comes down to what kernel is in the update vs what's in the main fedora updates stable release. The 36.20221005.0 update is quite old and the kernel will have long moved on (to 5.19.15-201.fc36) to what's in the compose from the 5th you're trying to move to.

You can enable the fedora archive repo which would mitigate this by enabling older kernel-modules-extra versions to be available. Fedora IoT does not enable this by default because it may allow downgrade attacks and so I believe this needs to be a explicit decision by the end user. EG there's WiFi mac80211 stack CVEs fixed in 5.19.15-201.fc36.

Is there a reason you're trying to deploy 36.20221005.0 vs latest?

Also what is the module(s) you need in kernel-modules-extra?

The output above is from latest; latest seems broken, too, which is another common occurrence. I tried 36.20221005.0, because it was the most recent release I saw upgrade successfully, but appears to be broken again. I use Fedora IoT as the OS for my k8s cluster, and I'd prefer to keep the nodes at a consistent release - typically I update one node, let it run for a few days, then rpm-ostree deploy the same release to the other nodes. The module I use from kernel-modules-extra is usbip_core.

Metadata Update from @pbrobinson:
- Issue close_status updated to: working as intended
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.