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.

Bug 1969627

Summary: umask failure during TASK: Install - Replica installation test
Product: Red Hat Enterprise Linux 8 Reporter: Mike Ralph <mralph>
Component: ansible-freeipaAssignee: Thomas Woerner <twoerner>
Status: CLOSED WONTFIX QA Contact: Varun Mylaraiah <mvarun>
Severity: high Docs Contact:
Priority: medium    
Version: 8.4CC: afarley, fcami, frenaud, ftrivino, mvarun, pcech, twoerner
Target Milestone: betaKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1984286 (view as bug list) Environment:
Last Closed: 2023-05-26 07:28:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1984286, 2185015    

Description Mike Ralph 2021-06-08 18:49:14 UTC
Description of problem: 
  When running the ansible-freeipa module on a RHEL 8.4 that has the STIG applied  I receive the error message "Unexpected system mask: 0077, expected 0022" during the task "ipareplica : Install - Replica installation test"


Version-Release number of selected component (if applicable): 
  ansible-freeipa-0.3.5-1.fc34.noarch


How reproducible:
  Constantly 


Steps to Reproduce:
1. run the ansible-freeipa install-cluster playbook
2.
3.

Actual results:
  TASK [ipareplica : Install - Replica installation test] **************
  fatal: [rep.lab18.example.com]: FAILED! => {"changed": false, "msg": 
  "Unexpected system mask: 0077, expected 0022"}

Expected results:
  Installation succeeds.

Additional info:

Comment 1 François Cami 2021-07-20 13:34:43 UTC
This is by design and totally expected.

Comment 2 Mike Ralph 2021-07-20 13:44:25 UTC
(In reply to François Cami from comment #1)
> This is by design and totally expected.

Then why does this not occur when the primary is installed, just the replica? Both machines are cloned from the same STIG'd VM.

Comment 5 François Cami 2021-07-20 14:29:32 UTC
Mike, so in short:

* using ipa-server-install / ipa-replica-install using a restrictive umask will not work,
* using ansible-freeipa, installing the primary works at the moment due to an oversight that will be fixed in the future.

Is there an interest in having more restrictive umasks supported? If so, could you please file a RFE?

Comment 7 Mike Ralph 2021-07-20 14:38:13 UTC
(In reply to François Cami from comment #5)
> Mike, so in short:
> 
> * using ipa-server-install / ipa-replica-install using a restrictive umask
> will not work,
> * using ansible-freeipa, installing the primary works at the moment due to
> an oversight that will be fixed in the future.
> 
> Is there an interest in having more restrictive umasks supported? If so,
> could you please file a RFE?

Considering that most, if not all, of the security frameworks require a more restrictive umask I would say it will be opened as a RFE.

But with that said, is there any reason why the umask has to be so loose?

Comment 8 François Cami 2021-07-20 14:43:04 UTC
> is there any reason why the umask has to be so loose?

Bugs were found in the past. IIRC the only tested umask is the default one.
Without continuous testing of more restrictive umasks, there is no guarantee that install would succeed or that all features would work/continue to work after upgrades.

Comment 24 RHEL Program Management 2023-05-26 07:28:19 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.