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.

Description of problem:
Attempting to perform new installs of RHEL7.2, and when choosing the "Pre-release Draft STIG for Redhat Linux 7 server", there is no automatic partitions created for /tmp, /home, /var, /var/log, or /var/log/audit.


Version-Release number of selected component (if applicable):
7.2


How reproducible:
Every time

Steps to Reproduce:
1. Select "Pre-release Draft STIG for Redhat Linux 7 server"
2. Select "Automatic Partitioning"
3. Select "Install"

Actual results:
Only / partition is created

Expected results:
Partitions are created for /, /tmp/, /home/, /var/, /var/log/, & /var/log/audit/

Additional info:
NOTE: This may be a problem with the delivered STIG not including the command to "fix" the partitioning, but not sure if the oscap anaconda addon would support it if it did.

Unfortunately, there's no way to create those partitions automatically because their sizes differ a lot with different use cases and storage configurations/setups/options.

I think the idea here was to verify that user defines compliant partitioning. And the plug-in can suggest to user that the partitioning selected is not compliant.

There is that a documentation for that feature at

  http://www.open-scap.org/tools/oscap-anaconda-addon/doc/
  Section 2.1. Partitioning rules

The problem is however, that scap-security-guide/STIG does not contain these rules. Vratislav, do you think we should have a bug against scap-security-guide to supply these rules?

(In reply to Šimon Lukašík from comment #3)
> I think the idea here was to verify that user defines compliant
> partitioning. And the plug-in can suggest to user that the partitioning
> selected is not compliant.
> 
> There is that a documentation for that feature at
> 
>   http://www.open-scap.org/tools/oscap-anaconda-addon/doc/
>   Section 2.1. Partitioning rules
> 
> The problem is however, that scap-security-guide/STIG does not contain these
> rules. Vratislav, do you think we should have a bug against
> scap-security-guide to supply these rules?

Yes please, it would definitely make user experience better.