Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature disparity between CIS-EL8 and EL9 #247

Closed
Thulium-Drake opened this issue Oct 24, 2024 · 2 comments
Closed

Feature disparity between CIS-EL8 and EL9 #247

Thulium-Drake opened this issue Oct 24, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@Thulium-Drake
Copy link
Contributor

Describe the Issue
In the RHEL8 version of this role, control 1.1.7.4 and 1.1.7.5 exist that enforce user- and group quota's on the mount for /home.

In the RHEL9 version of the role, this is no longer the case and (in my case) running the role actively removes these mount options, leaving systems configured differently.

Is that intended by the CIS guidelines (and should I change my config)?

Expected Behavior
Both systems behave the same with regards of configuring mounts.

Actual Behavior
In my environment I am managing filesystem mounts with a role for both RHEL8 and RHEL9, but there's a idempotency issue right now :-)

Control(s) Affected
1.1.7.4 and 1.1.7.5 (if they exist in RHEL9)

Environment (please complete the following information):

  • branch being used: master
  • Ansible Version: 2.16
  • Host Python Version: 3.12
  • Ansible Server Python Version: 3.9.18
  • Additional Details:

Possible Solution
If not mandatory, can we have a means of adding these mount options manually? :-)

@Thulium-Drake Thulium-Drake added the bug Something isn't working label Oct 24, 2024
@uk-bolly uk-bolly self-assigned this Nov 4, 2024
@uk-bolly
Copy link
Member

uk-bolly commented Nov 4, 2024

hi @Thulium-Drake

Thanks as always fro your feedback. I am working on this currently hoping to have the PR raised asap.

Kindest regards

uk-bolly

@uk-bolly
Copy link
Member

hi @Thulium-Drake

Thank you again for this issue. The fix has been applied and is now in the main branch and release. I will close this issue, Please reopen if you feel this is not resolved.

Many thanks

uk-bolly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants