-
Bug
-
Resolution: Unresolved
-
Normal
-
CentOS Stream 10, rhel-10.0
-
selinux-policy-40.13.17-1.el10
-
No
-
Moderate
-
1
-
rhel-sst-security-selinux
-
ssg_security
-
20
-
1
-
False
-
-
No
-
SELINUX 241127 - 241218
-
Unspecified Release Note Type - Unknown
-
None
What were you trying to do that didn't work?
Register a system using the Ansible rhc-system-role.
What is the impact of this issue to you?
The system cannot be registered to RHSM using tooling that communicates with rhsmcertd.
Please provide the package NVR for which the bug is seen:
I believe this is present in selinux-policy-40.13.13-1.el10
How reproducible is this bug?:
Always
Steps to reproduce
- Create a RHEL 10 machine
- Run the attached playbook to register the system using an Ansible role rhc-system-role.yaml
Expected results
The playbook should succeed.
Actual results
The playbook exits with an error:
FAILED! => {"changed": false, "msg": "Failed to register with 'subscription.rhsm.stage.redhat.com': com.redhat.RHSM1.Error: {\"exception\": \"PermissionError\", \"severity\": \"error\", \"message\": \"[Errno 1] Operation not permitted: '/etc/pki/consumer/key.pem'\"}"}
Additional Information
This was fixed via a PR to upstream project in October. To fix this, that PR needs to be back-ported into c10s.
- links to
-
RHBA-2024:140162 selinux-policy bug fix and enhancement update