Bug 2183279
| Summary: | systemd-udev resolving to systemd-boot-unsigned after split | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Neil Hanlon <neil> |
| Component: | dnf | Assignee: | Marek Blaha <mblaha> |
| Status: | CLOSED MIGRATED | QA Contact: | swm-qe |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | CentOS Stream | CC: | bstinson, carl, daan.j.demeyer, jamacku, james.antill, jwboyer, kwalker, noonedeadpunk, systemd-maint-list, zbyszek |
| Target Milestone: | rc | Keywords: | MigratedToJIRA, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-21 16:31:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Neil Hanlon
2023-03-30 17:47:32 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? 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. I was able to reproduce the issue using the centos/centos:stream9 container. 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. 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. 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. 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 :) *** Bug 2229539 has been marked as a duplicate of this bug. *** The issue is fixed by https://github.com/rpm-software-management/libdnf/pull/1624 and https://github.com/rpm-software-management/dnf/pull/1994 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. 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. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |