Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionmkielian@redhat.com
2023-02-15 22:14:32 UTC
Created attachment 1944429[details]
RHEL 9.0 DIS STIG GUI - upower broken
Description of problem:
When applying Security Profile: [ DRAFT] DISA STIG with GUI for Red Hat Enterprise Linux 9
The upower service fails to start
Version-Release number of selected component (if applicable):
Red Hat Enterprise 9.0
Red Hat Enterprise 9.1
How reproducible: Always
Steps to Reproduce:
1. Install a fresh RHEL 9.x system
Note: Tested on KVM 2 CPUs 2GB RAM
Create the following partitions: ( To comply with DISA STIG )
Setup with 20GB disk size
Select "Custom", click Done
Use: Create partition button to create then add the following: "Click here to create them automatically"
/home - 2GB
/tmp - 1GB
/var - 2GB
/var/log/ - 2GB
/var/log/audit - 1GB
/var/tmp - 1GB
Remainder of space to / ( root partiton ) ~ 8GB
2. Select the Security profiles:
Use: [ DRAFT] DISA STIG with GUI for Red Hat Enterprise Linux 9
Click select Profiles button
The bottom window should display the changes made.
Finish install an
3. Check the Status of upower service
Upon logging in and running
# systemctl status upower
Actual results:
Feb 14 13:23:43 localhost systemd[1]: Starting Daemon for power management...
Subject: A start job for unit upower.service has begun execution
Defined-By: systemd
Support: https://access.redhat.com/support
A start job for unit upower.service has begun execution.
The job identifier is 317.
Feb 14 13:23:43 localhost systemd[1047]: upower.service: Failed to set up user namespacing: No space left on device
Feb 14 13:23:43 localhost systemd[1047]: upower.service: Failed at step USER spawning /usr/libexec/upowerd: No space left on device
Subject: Process /usr/libexec/upowerd could not be executed
Defined-By: systemd
Support: https://access.redhat.com/support
The process /usr/libexec/upowerd could not be executed and failed.
Expected results:
upower service should be running and showing as active:
EXAMPLE: ( From RHEL 8 CSB Build )
$ systemctl status upower
- upower.service - Daemon for power management
Loaded: loaded (/usr/lib/systemd/system/upower.service; disabled; vendor preset: enabled)
Active: active (running) since Sun 2023-02-05 18:41:53 MST; 1 weeks 2 days ago
Docs: man:upowerd(8)
Main PID: 5919 (upowerd)
Tasks: 3 (limit: 202556)
Memory: 2.3M
CGroup: /system.slice/upower.service
└─5919 /usr/libexec/upowerd
Additional info:
See attached sosreport from both RHEL 9.0 and RHEL 9.1 systems.
The security profile seems to disable user namespacing, which means systemd can't launch the service at all:
Feb 14 13:23:43 localhost systemd[1047]: upower.service: Failed to set up user namespacing: No space left on device
upower isn't even run.
user namespacing is used by systemd to provide upower with some sandboxing which protects the system from being made vulnerable if upower were to have bugs that weakened its security. This problem will also impact a lot of other daemons that also use systemd's sandboxing to minimise their attack surface.
Reassigning to systemd so they can figure out a better error message for this problem, and reassign to the security profile if needed.
Comment 3RHEL Program Management
2023-09-21 12:16:52 UTC
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.
Comment 4RHEL Program Management
2023-09-21 12:20:16 UTC
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.