This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2183279 - systemd-udev resolving to systemd-boot-unsigned after split
Summary: systemd-udev resolving to systemd-boot-unsigned after split
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: dnf
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Marek Blaha
QA Contact: swm-qe
URL:
Whiteboard:
: 2229539 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-30 17:47 UTC by Neil Hanlon
Modified: 2024-01-20 04:25 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 16:31:48 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-6304 0 None Migrated None 2023-09-21 16:31:58 UTC
Red Hat Issue Tracker RHELPLAN-153647 0 None None None 2023-03-30 17:48:10 UTC

Description Neil Hanlon 2023-03-30 17:47:32 UTC
Description of problem:

systemd 252-8 added Obseletes on itself between -boot-unsigned and -udev due to some files being split between these two subpackages.

Ideally, the newer NEVR (252-14) would allow -udev to be installed, but in testing, systemd-udev still resolves to systemd-boot-unsigned even with the -14 RPMs in a repository together.

Version-Release number of selected component (if applicable): 252-8, 252-14


How reproducible: Always

Steps to Reproduce:
1. dnf config-manager --set-enabled crb
2. dnf install systemd-udev

Actual results:

systemd-udev package is installed

Expected results:

systemd-boot-unsigned is installed instead.

Additional info:

[root@255594769a63 /]# dnf -y install systemd-udev
Dependencies resolved.
==========================================================================================================================
 Package                                 Architecture             Version                     Repository             Size
==========================================================================================================================
Installing:
 systemd-boot-unsigned                   x86_64                   252-8.el9                   crb                   124 k

Transaction Summary
==========================================================================================================================
Install  1 Package


[root@255594769a63 /]# ls a
repodata                       systemd-libs-252-14.el9.x86_64.rpm  systemd-udev-252-14.el9.x86_64.rpm
systemd-252-14.el9.x86_64.rpm  systemd-pam-252-14.el9.x86_64.rpm
[root@255594769a63 /]# dnf --repofrompath=a,/a/ install systemd-udev
Added a repo from /a/
Last metadata expiration check: 0:00:16 ago on Thu Mar 30 17:46:54 2023.
Dependencies resolved.
==========================================================================================================================
 Package                                 Architecture             Version                     Repository             Size
==========================================================================================================================
Installing:
 systemd-boot-unsigned                   x86_64                   252-8.el9                   crb                   124 k

Comment 1 Dmitriy Rabotjagov 2023-05-30 12:49:18 UTC
Hey folks, any updates on this one?

As it's quite unpleasant packaging bug with not straightforward workaround, that supposedly should be relatively easy to fix as it's more about metadata of packages rather then their content?

Comment 2 Jan Macku 2023-05-31 08:41:10 UTC
Hello,

May I ask what your use case is? On a regular system, systemd-udev is always installed, and I wouldn't recommend uninstalling it. Are you using containers with systemd-udev?

Thanks
I'm going to investigate.

Comment 3 Jan Macku 2023-05-31 10:36:17 UTC
I was able to reproduce the issue using the centos/centos:stream9 container.

Comment 4 Dmitriy Rabotjagov 2023-05-31 11:20:31 UTC
Hey,

Yes, usecase is exactly container image. Or the ones, that are built using `dnf --installroot=/var/lib/machines/container_name install --nodocs rootfiles coreutils dnf`

Then we're trying to install gluster inside the container and use `systemd-tmpfiles-setup-dev.service` that is provided by systemd-udev package, that requires a nasty workaround to get installed for couple of months now.

Comment 5 Zbigniew Jędrzejewski-Szmek 2023-05-31 12:32:30 UTC
We encountered this in Fedora too: https://bugzilla.redhat.com/show_bug.cgi?id=2176263.
It was fixed for both dnf and dnf5 via updates.

Comment 6 Jan Macku 2023-05-31 12:50:09 UTC
Dmitriy,
You can use `dnf install systemd-udev-252-15.el9` as a workaround for now.

I'm going to move this bug to dnf. Please see the comment from Zbigniew above.

Comment 7 Dmitriy Rabotjagov 2023-05-31 14:08:50 UTC
Yeah, I'm aware of workaround, but as I said earlier - it's quite nasty.
So eventually it hit our users on stable releases of our tooling, so we have to retroactively backport patches to fix the regression. But now we also need to keep track on versions that are provided and update systemd-udev version in the code each time new one is being released and backport that to all stable branches that have support of CentOS 9 Stream, which is quite a PITA. Or, add extra steps to check mirrors for available packages, parse them and apply versioning in place, which I'd love avoid frankly speaking.

So thanks for taking time to look into that, hopefully it will be fixed soonish :)

Comment 9 Lukáš Nykrýn 2023-08-07 10:36:37 UTC
*** Bug 2229539 has been marked as a duplicate of this bug. ***

Comment 12 Marek Blaha 2023-09-21 06:58:38 UTC
Test is in https://github.com/rpm-software-management/ci-dnf-stack/pull/1388

Comment 13 RHEL Program Management 2023-09-21 16:28:42 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 14 RHEL Program Management 2023-09-21 16:31:48 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 15 Red Hat Bugzilla 2024-01-20 04:25:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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