Bug 2112366

Summary:	Stalld is running in unconfined_service_t type
Product:	Red Hat Enterprise Linux 8	Reporter:	Chen <cchen>
Component:	stalld	Assignee:	Leah Leshchinsky <lleshchi>
Status:	CLOSED ERRATA	QA Contact:	Chang Yin <cyin>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.8	CC:	bhu, blitton, cgaynor, cyin, jkacur, jmencak, lleshchi, mstowell, rt-qe, shichen, sizucchi
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	stalld-1.17-2.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2126494 2126495 2126496 (view as bug list)		Environment:
Last Closed:	2023-05-16 08:15:52 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:
Bug Depends On:
Bug Blocks:	2126494, 2126495, 2126496

Description Chen 2022-07-29 14:02:07 UTC

Description of problem:

This is the continuous discussion for bz 2111030. Stalld is running as unconfined_service_t type, which violates some compliance rules shipped in OpenShift

Version-Release number of selected component (if applicable):

stalld-1.10-1.el8_4.x86_64

How reproducible:

100%

Steps to Reproduce:
1. yum install stalld
2. ps -eZ | grep stalld
3.

Actual results:


Expected results:


Additional info:

I can confirm quickly adding "/bin/sh -c" in front of ExecStart in systemd unit file could simply change the unconfined_service_t to initrc_t.

Comment 11 Chen 2022-08-27 15:05:45 UTC

Thanks a lot Jiri for your confirm!

@Leah we got confirm from NTO developer that NTO's stalld system unit source is RHEL not its own MachineConfig.

Best Regards,
Chen

Comment 30 Chen 2022-09-14 06:58:43 UTC

Hi Colum,

We are tracking this issue in 8.4-z stream in this bz 2126496. For estimate time I think perhaps developer team has more accurate answer. By looking at c#27 seems for next minor release of 8.4-z will pick this fix up but better to wait for @lleshchi 's confirm. Leah could you please help us to figure out whether there is an ETA for this fix if any ?

Speaking of whether it's a blocker for Nokia or not, technically it is definitely not a blocker because this issue only violates a compliance check and it doesn't break any functions for OCP. But if Nokia insists this issue is blocking their product release, for example, if this compliance issue is not resolved then their product can not be released, it could be a blocker for Nokia. From Red Hat's point of view, it is not a blocker but it depends on Nokia's internal policy.

Best Regards,
Chen

Comment 39 errata-xmlrpc 2023-05-16 08:15:52 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (stalld bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2751