-
Story
-
Resolution: Duplicate
-
Undefined
-
None
-
rhel-9.3.0
-
None
-
sst_installer
-
ssg_front_door
-
None
-
False
-
-
None
-
None
-
None
-
None
-
x86_64
-
None
What were you trying to do that didn't work?
I'm currently experimenting with a RHEL9 derivative (Alamalinux) and kickstart with the CIS server workstation level 2 set.
This requires some mount-points (including /dev/shm) to be on a different partition.
/dev/shm is by default on a tmpfs (and should stay like that I guess) and is automounted by default during boot (even if not defined in the fstab)
The CIS profiles REQUIRES that /dev/shm is defined in the fstab. So here is the 1st question, as it's automounted, should that really be the case?
I've added `part /dev/shm --fstype="tmpfs" --size=1024` to the kickstart file and the CIS profile is happy, but
- the `--size` option is mandatory, otherwise anaconda fails with a python trace
- `tmpfs`is not documented in RH documentation as being a supported fstype
- The fstab entry on the installed machine seems boggus:
`tmpfs /dev/shm tmpfs defaults,size=1024m,size=1024m,nodev,noexec,nosuid,size=1024m,size=1024m,size=1024m,size=1024m,size=1024m 0 0`
Please provide the package NVR for which bug is seen:
How reproducible:
Always
Steps to reproduce
- Create a kickstart file that enable CIS server L2 hardening
- Add `part /dev/shm --fstype="tmpfs" --size=1024` so anaconda is happy to install
- look at the /etc/fstab on the resulting machine
Expected results
`tmpfs /dev/shm tmpfs defaults,size=1024m,nodev,noexec,nosuid 0 0`
Actual results
`tmpfs /dev/shm tmpfs defaults,size=1024m,size=1024m,nodev,noexec,nosuid,size=1024m,size=1024m,size=1024m,size=1024m,size=1024m 0 0`
I can open other bugs for the other problem if you want
- duplicates
-
RHEL-16801 Selecting "CIS Red Hat Enterprise Linux 9 Benchmark for Level 1 - Server" profile during RHEL 9.3 install fails
- Closed