package_managers: Oracle's UEK kernels are reported as an interrupted dnf transaction #107

Closed
opened 2026-11-12 09:28:12 +00:00 by christianmanivong · 0 comments
Owner

What happens

On an Oracle Linux 9 host with more than one UEK kernel installed, the host status reports the package manager as interrupted. netOrk then shows "Paketverwaltung unterbrochen" (error):

dnf hat kernel-uek (duplicate), kernel-uek-modules (duplicate), kernel-uek-modules-core (duplicate), kernel-uek-modules-desktop (duplicate), kernel-uek-modules-extra-netfilter (duplicate) und 2 weitere halb fertig zurückgelassen.

sudo dnf check finds nothing wrong. Seen on build-arm-01 (OL 9.8, aarch64, dnf 4.14.0, libdnf 0.69.0), which has three kernels, as installonly_limit=3 allows.

Cause

_RPM_PART asks rpm which packages provide dnf's upstream default installonlypkgs (_INSTALLONLY: kernel, installonlypkg(kernel), …) plus what dnf.conf adds. Oracle builds more into libdnf's defaults:

kernel, kernel-PAE, installonlypkg(kernel), installonlypkg(kernel-module), installonlypkg(vm), multiversion(kernel), kernel-uek, installonlypkg(kernel-uek), multiversion(kernel-uek), installonlypkg(kernel-uek-core), …, installonlypkg(kernel-uek-modules), …

The UEK packages provide only those (kernel-uek-core provides installonlypkg(kernel-uek-core), the kernel-uek-modules-* packages provide installonlypkg(kernel-uek-modules), and kernel-uek provides nothing like that at all). None of them matches upstream's list, so all eight are counted as duplicates.

Fix

Read the defaults the host's libdnf was built with, through its Python binding (libdnf.conf.ConfigMain().installonlypkgs()), and add them to the query. Upstream's list stays the floor where libdnf cannot be asked (dnf 5, yum).

Reported from NetOrk/netork (device build-arm-01).

## What happens On an Oracle Linux 9 host with more than one UEK kernel installed, the host status reports the package manager as interrupted. netOrk then shows "Paketverwaltung unterbrochen" (error): > dnf hat kernel-uek (duplicate), kernel-uek-modules (duplicate), kernel-uek-modules-core (duplicate), kernel-uek-modules-desktop (duplicate), kernel-uek-modules-extra-netfilter (duplicate) und 2 weitere halb fertig zurückgelassen. `sudo dnf check` finds nothing wrong. Seen on build-arm-01 (OL 9.8, aarch64, dnf 4.14.0, libdnf 0.69.0), which has three kernels, as `installonly_limit=3` allows. ## Cause `_RPM_PART` asks rpm which packages provide dnf's *upstream* default `installonlypkgs` (`_INSTALLONLY`: `kernel`, `installonlypkg(kernel)`, …) plus what `dnf.conf` adds. Oracle builds more into libdnf's defaults: ``` kernel, kernel-PAE, installonlypkg(kernel), installonlypkg(kernel-module), installonlypkg(vm), multiversion(kernel), kernel-uek, installonlypkg(kernel-uek), multiversion(kernel-uek), installonlypkg(kernel-uek-core), …, installonlypkg(kernel-uek-modules), … ``` The UEK packages provide only those (`kernel-uek-core` provides `installonlypkg(kernel-uek-core)`, the `kernel-uek-modules-*` packages provide `installonlypkg(kernel-uek-modules)`, and `kernel-uek` provides nothing like that at all). None of them matches upstream's list, so all eight are counted as duplicates. ## Fix Read the defaults the host's libdnf was built with, through its Python binding (`libdnf.conf.ConfigMain().installonlypkgs()`), and add them to the query. Upstream's list stays the floor where libdnf cannot be asked (dnf 5, yum). Reported from NetOrk/netork (device build-arm-01).
christianmanivong added the
prio
P2
bug
labels 2026-11-12 09:28:12 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: NAPALM/napalm-device-types#107