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 1895435 - Adding DISA STIG during OS installation causes 'ipa-server-install' to fail
Summary: Adding DISA STIG during OS installation causes 'ipa-server-install' to fail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: fapolicyd
Version: 8.3
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Radovan Sroka
QA Contact: Dalibor Pospíšil
URL:
Whiteboard:
Depends On:
Blocks: 1905895
TreeView+ depends on / blocked
 
Reported: 2020-11-06 16:43 UTC by aheverle
Modified: 2024-03-25 16:58 UTC (History)
8 users (show)

Fixed In Version: fapolicyd-1.0.2-2.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1905895 (view as bug list)
Environment:
Last Closed: 2021-05-18 16:22:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
install log from test server (280.29 KB, text/plain)
2020-11-06 16:43 UTC, aheverle 		no flags Details
View All

Description aheverle 2020-11-06 16:43:02 UTC 
Created attachment 1727184 [details]
install log from test server

Description of problem:
When adding the DISA STIG security profile during OS installation causes 'ipa-server-install' to fail

Version-Release number of selected component (if applicable):
ipa-server-4.8.7-13.module+el8.3.0+8376+0bba7131.x86_64

How reproducible:
Everytime

Steps to Reproduce:
1.  Add DISA security profile in OS installation UI
2.  Attempt to install IDM


Actual results:
Failure

Expected results:
Success

Additional info:
A couple of things I have noticed during my testing.  

 1 - If you install the OS, enable FIPS post OS installation via CLI, and then execute 'ipa-server-install' it is successful.

 2 - During the failed attempt, I was prompted to confirm I wanted to proceed with the installation with the modified umask from the STIG.  I was not prompted for this change when I enabled FIPS via CLI.

Error install log:

DEBUG: Command: sudo -u pkiuser /usr/lib/jvm/jre-openjdk/bin/java -classpath /usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/tomcat-servlet-api.jar:/usr/share/pki/ca/webapps/ca
/WEB-INF/lib/*:/var/lib/pki/pki-tomcat/common/lib/*:/usr/share/pki/lib/* -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -Dcatalina.base=/var/lib/pki/pk
i-tomcat -Dcatalina.home=/usr/share/tomcat -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/lib/pki/pki-tomcat/temp -Djava.util.logging.config.file=/etc/pki/pki-tomcat/logging.properties 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Dcom.redhat.fips=false org.dogtagpki.server.cli.PKIServerCLI ca-db-remove --force --debug
Error: Could not find or load main class org.dogtagpki.server.cli.PKIServerCLI
ERROR: CalledProcessError: Command '['sudo', '-u', 'pkiuser', '/usr/lib/jvm/jre-openjdk/bin/java', '-classpath', '/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/tomcat-servlet
-api.jar:/usr/share/pki/ca/webapps/ca/WEB-INF/lib/*:/var/lib/pki/pki-tomcat/common/lib/*:/usr/share/pki/lib/*', '-Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourc
eFactory', '-Dcatalina.base=/var/lib/pki/pki-tomcat', '-Dcatalina.home=/usr/share/tomcat', '-Djava.endorsed.dirs=', '-Djava.io.tmpdir=/var/lib/pki/pki-tomcat/temp', '-Djava.util.logg
ing.config.file=/etc/pki/pki-tomcat/logging.properties', '-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager', '-Dcom.redhat.fips=false', 'org.dogtagpki.server.cli.PKI
ServerCLI', 'ca-db-remove', '--force', '--debug']' returned non-zero exit status 1.
  File "/usr/lib/python3.6/site-packages/pki/server/pkispawn.py", line 575, in main
    scriptlet.spawn(deployer)
  File "/usr/lib/python3.6/site-packages/pki/server/deployment/scriptlets/configuration.py", line 820, in spawn
    subsystem.remove_database(force=True)
  File "/usr/lib/python3.6/site-packages/pki/server/subsystem.py", line 945, in remove_database
    self.run(cmd, as_current_user=as_current_user)
  File "/usr/lib/python3.6/site-packages/pki/server/subsystem.py", line 1137, in run
    subprocess.run(cmd, check=True)
  File "/usr/lib64/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
Comment 1 Florence Blanc-Renaud 2020-11-09 12:52:38 UTC 
Re-assigning to pki-core component as the issue happens during the pkispawn step of ipa-server-install.
Comment 36 errata-xmlrpc 2021-05-18 16:22:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (fapolicyd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1952
Note You need to log in before you can comment on or make changes to this bug.