Bug 2100211

Summary:	systemd is included in the ubi9 and ubi9-minimal image, is this intended and if so why?
Product:	Red Hat Enterprise Linux 9	Reporter:	Matt Mezynski <mmezynsk>
Component:	ubi9-minimal-container	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED DUPLICATE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	dornelas, jwboyer
Target Milestone:	rc	Keywords:	Reopened
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-22 21:02:06 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 Matt Mezynski 2022-06-22 17:55:45 UTC

Description of problem:
systemd is included in the ubi9 and ubi9-minimal image, is this intended and if so why?

Version-Release number of selected component (if applicable):
ubi9 and ubi9-minimal images

How reproducible:
always

Steps to Reproduce:
1. Note that systemd is provided in:

https://catalog.redhat.com/software/containers/ubi9/618326f8c0d15aff4912fe0b?container-tabs=packages

https://catalog.redhat.com/software/containers/ubi9-minimal/61832888c0d15aff4912fe0d?container-tabs=packages

Actual results:
systemd is in the ubi9 and ubi9-minimal package set

Expected results:
Unsure if this was a design choice difference from ubi8 and ubi8-minimal

Additional info:
N/A

Comment 2 Josh Boyer 2022-06-22 18:44:55 UTC

ubi8 also includes systemd.

[jwboyer@vader ~]$ podman pull ubi8
Trying to pull registry.access.redhat.com/ubi8:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob 1b890c73c3cf done  
Copying blob de63ba066b7c done  
Copying config 88c8870492 done  
Writing manifest to image destination
Storing signatures
88c8870492b3eb59d6c272244e0f5e8e924450e05216546ad710d276b9e6e2d3
[jwboyer@vader ~]$ podman run -it --rm ubi8
[root@584ff689e674 /]# rpm -q systemd
systemd-239-58.el8.x86_64
[root@584ff689e674 /]# 

ubi8-minimal and ubi9-minimal both include systemd-libs, which provides the libudev library.  The main systemd package is not included in either minimal image.


[jwboyer@vader ~]$ podman run -it --rm ubi9-minimal
[root@1ca52576f52e /]# rpm -q systemd
package systemd is not installed
[root@1ca52576f52e /]#

Comment 3 Derrick Ornelas 2022-06-22 18:59:01 UTC

It's not 100% clear in the description, but having spoken to Matt about this issue I know the real question is about why systemd is included in ubi9-minimal when it's not in ubi8-minimal.  


# podman run --pull=always --rm -ti ubi9-minimal
Trying to pull registry.access.redhat.com/ubi9-minimal:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob a0f87b8b1a43 skipped: already exists  
Copying blob 37851b0666df skipped: already exists  
Copying config 45c4bec5e9 done  
Writing manifest to image destination
Storing signatures

[root@db0ba1c3baf9 /]# rpm -q systemd
systemd-250-6.el9_0.x86_64


[root@db0ba1c3baf9 /]# rpm -q --whatrequires systemd | uniq
device-mapper-1.02.183-4.el9.x86_64
systemd-pam-250-6.el9_0.x86_64
dbus-common-1.12.20-5.el9.noarch
dbus-broker-28-5.el9.x86_64
openldap-2.4.59-4.el9_0.x86_64


After some digging I believe this is related:

  Bug 2074672 - OpenLDAP pulls in systemd in the minimal installation


I think device-mapper is pulled in by cryptsetup-libs which is pulled in by systemd.  And, dbus, etc is also pulled in by systemd.

Comment 4 Josh Boyer 2022-06-22 19:24:05 UTC

(In reply to Derrick Ornelas from comment #3)
> It's not 100% clear in the description, but having spoken to Matt about this
> issue I know the real question is about why systemd is included in
> ubi9-minimal when it's not in ubi8-minimal.  
> 
> 
> # podman run --pull=always --rm -ti ubi9-minimal
> Trying to pull registry.access.redhat.com/ubi9-minimal:latest...
> Getting image source signatures
> Checking if image destination supports signatures
> Copying blob a0f87b8b1a43 skipped: already exists  
> Copying blob 37851b0666df skipped: already exists  
> Copying config 45c4bec5e9 done  
> Writing manifest to image destination
> Storing signatures
> 
> [root@db0ba1c3baf9 /]# rpm -q systemd
> systemd-250-6.el9_0.x86_64

OK, that is odd.  I don't see it in the internal images so perhaps it's already resolved.

> [root@db0ba1c3baf9 /]# rpm -q --whatrequires systemd | uniq
> device-mapper-1.02.183-4.el9.x86_64
> systemd-pam-250-6.el9_0.x86_64
> dbus-common-1.12.20-5.el9.noarch
> dbus-broker-28-5.el9.x86_64
> openldap-2.4.59-4.el9_0.x86_64
> 
> 
> After some digging I believe this is related:
> 
>   Bug 2074672 - OpenLDAP pulls in systemd in the minimal installation

OK.  Either way, there's nothing for the images to resolve here.  The answer is "it's a dependency of something" and the fix would be to remove that dependency.

Comment 5 Derrick Ornelas 2022-06-22 21:02:06 UTC

I do think you're right that it's resolved in Stream and the latest RHEL openldap build

rpm -qp --requires ./openldap-2.4.59-5.el9.x86_64.rpm | grep systemd | wc -l
0



I'll close this as a duplicate of BZ 2074672

*** This bug has been marked as a duplicate of bug 2074672 ***