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 1480609 - ipa-replica-install failings when minssf is set to 56 on the idm master
Summary: ipa-replica-install failings when minssf is set to 56 on the idm master
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.0
Hardware: All
OS: All
medium
medium
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-11 13:36 UTC by aheverle
Modified: 2020-11-30 14:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 14:14:45 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description aheverle 2017-08-11 13:36:38 UTC
Description of problem:
Customer has minssff set to 56 on the IDM master, due to PCI compliance.

Replica install is failing with 

Version-Release number of selected component (if applicable):
ipa-server-4.4.0-14.el7_3.7.x86_64

How reproducible:
Everytime

Steps to Reproduce:
1. ipa-replica-install
2.
3.

Actual results:
 [26/40]: creating DS keytab
  [27/40]: setting up initial replication
  [error] DatabaseError: Server is unwilling to perform: Minimum SSF not met.
Your system may be partly configured.
Run /usr/sbin/ipa-server-install --uninstall to clean up.

ipa.ipapython.install.cli.install_tool(CompatServerReplicaInstall): ERROR    Server is unwilling to perform: Minimum SSF not met.
ipa.ipapython.install.cli.install_tool(CompatServerReplicaInstall): ERROR    The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information

Expected results:
replica install to complete

Additional info:

On the IDM master, ldapsearches are failing due to the same issue.

[root@avid4p03 ~]# ldapsearch -D "cn=directory manager" -W -b "dc=example,dc=com" "(nsds5replconflict=*)"
Enter LDAP Password:
# extended LDIF
#
# LDAPv3
# base <dc=example,dc=com> with scope subtree
# filter: (nsds5replconflict=*)
# requesting: ALL
#

# search result
search: 2
result: 53 Server is unwilling to perform
text: Minimum SSF not met.

[root@avid4p03 ~]# grep minssf /etc/dirsrv/slapd-EXAMPLE-COM/dse.ldif
nsslapd-minssf: 56
nsslapd-minssf-exclude-rootdse: on

Comment 2 Rob Crittenden 2017-08-11 15:41:35 UTC
Note that the ldapsearch is failing because it isn't requesting any security. Add -Z to your cli to enable start_tls.

Comment 8 Petr Vobornik 2017-10-13 16:12:13 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/7195

Comment 13 Petr Čech 2020-11-30 14:14:45 UTC
This BZ has been evaluated multiple times over the last several years and we assessed that it is a valuable request to keep in the backlog and address it at some point in future. Time showed that we did not have such capacity, nor have it now nor will have in the foreseeable future. In such a situation keeping it in the backlog is misleading and setting the wrong expectation that we will be able to address it. Unfortunately we will not. To reflect this we are closing this BZ. If you disagree with the decision please reopen or open a new support case and create a new BZ. However this does not guarantee that the request will not be closed during the triage as we are currently applying much more rigor to what we actually can accomplish in the foreseeable future. Contributions and collaboration in the upstream community and CentOS Stream is always welcome!
Thank you for understanding
Red Hat Enterprise Linux Identity Management Team


Note You need to log in before you can comment on or make changes to this bug.