-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-9.5
-
rhel-system-roles-1.99.1-0.1.el9
-
No
-
Low
-
rhel-system-roles
-
0
-
QE ack, Dev ack
-
False
-
False
-
-
Yes
-
Red Hat Enterprise Linux
-
None
-
Pass
-
Automated
-
Bug Fix
-
-
Done
-
Done
-
Done
-
Not Required
-
None
What were you trying to do that didn't work?
We are using the role to unmask, enable and start, however, if the unit is masked, we cannot enable, start until umask.
What is the impact of this issue to you?
Customer is having to run the role twice, first to umaks, secondly to enable/start the services
Please provide the package NVR for which the bug is seen:
rhel-system-roles-1.88.9-0.1.el9_5.noarch
How reproducible is this bug?:
Mask some units and run the role to with the following variables.
roles: - role: rhel-system-roles.systemd vars: systemd_unmasked_units: - autofs.service - rpcbind.service - rpcbind.socket systemd_enabled_units: - autofs.service - rpcbind.service systemd_started_units: - autofs.service - rpcbind.service
Steps to reproduce
- mask autofs or rpcbind
- run the role
Expected results
We should be able to umask the units previous to start.
Actual results
It fails to start if we do not umask it previously.
- links to
-
RHEA-2025:148880 rhel-system-roles bug fix and enhancement update