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 1075165

Summary: ipa-replica-install never checks for 7389 port
Product: Red Hat Enterprise Linux 7 Reporter: Martin Kosek <mkosek>
Component: ipaAssignee: Martin Kosek <mkosek>
Status: CLOSED CURRENTRELEASE QA Contact: Namita Soman <nsoman>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.0CC: dpal, mkosek, rcritten, spoore
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-3.3.3-22.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 11:04:34 UTC Type: ---
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: 1073810    

Description Martin Kosek 2014-03-11 15:48:28 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/4240

This is a follow up for #4213.

When creating replica from a Dogtag 9 based IPA server, the port 7389 which is required for the installation is never checked by `ipa-replica-conncheck` even though it knows that it is being installed from the Dogtag 9 based FreeIPA. If the 7389 port would be blocked by firewall, installation would stuck with no hint to user.

Comment 3 Scott Poore 2014-03-18 22:41:59 UTC
Just to clarify, to test this, we will have to test against a RHEL6 IPA master, right?

Comment 4 Scott Poore 2014-03-19 03:01:30 UTC
Ok, I tested with ipa-server-3.3.3-18.el7 to successfully reproduce the issue with a RHEL 6.5 IPA Master:


[root@replica1 ~]# ipa-replica-install -U --setup-ca --setup-dns --forwarder=$DNSFORWARD \
>     -w Secret123 -p Secret123  /dev/shm/replica-info-$REPLICA1.gpg
Run connection check to master
Check connection from replica to remote master 'master.ipa1075165.example.test':
   Directory Service: Unsecure port (389): OK
   Directory Service: Secure port (636): OK
   Kerberos KDC: TCP (88): OK
   Kerberos Kpasswd: TCP (464): OK
   HTTP Server: Unsecure port (80): OK
   HTTP Server: Secure port (443): OK

The following list of ports use UDP protocol and would need to be
checked manually:
   Kerberos KDC: UDP (88): SKIPPED
   Kerberos Kpasswd: UDP (464): SKIPPED

Connection from replica to master is OK.
Start listening on required ports for remote master check
Get credentials to log in to remote master
Check SSH connection to remote master
Execute check on remote master
Check connection from master to remote replica 'replica1.ipa1075165.example.test':
   Directory Service: Unsecure port (389): OK
   Directory Service: Secure port (636): OK
   Kerberos KDC: TCP (88): OK
   Kerberos KDC: UDP (88): OK
   Kerberos Kpasswd: TCP (464): OK
   Kerberos Kpasswd: UDP (464): OK
   HTTP Server: Unsecure port (80): OK
   HTTP Server: Secure port (443): OK

Connection from master to replica is OK.

Connection check OK
ipa         : CRITICAL CA DS schema check failed. Make sure the PKI service on the remote master is operational.

Your system may be partly configured.
Run /usr/sbin/ipa-server-install --uninstall to clean up.

Can't contact LDAP server

Comment 5 Scott Poore 2014-03-19 03:07:01 UTC
Verified.

Version ::

ipa-server-3.3.3-25.el7.x86_64

Results ::

IPA Master setup on RHEL 6.5 server and ipa-replica-prepare run and copied to RHEL 7.0 replica server.  Then result below:

[root@replica1 ~]# ipa-replica-install -U --setup-ca --setup-dns --forwarder=$DNSFORWARD     -w Secret123 -p Secret123  /dev/shm/replica-info-$REPLICA1.gpg
Run connection check to master
Check connection from replica to remote master 'master.ipa1075165.example.test':
   Directory Service: Unsecure port (389): OK
   Directory Service: Secure port (636): OK
   Kerberos KDC: TCP (88): OK
   Kerberos Kpasswd: TCP (464): OK
   HTTP Server: Unsecure port (80): OK
   HTTP Server: Secure port (443): OK
   PKI-CA: Directory Service port (7389): FAILED
Port check failed! Inaccessible port(s): 7389 (TCP)
Connection check failed!
Please fix your network settings according to error messages above.
If the check results are not valid it can be skipped with --skip-conncheck parameter.

Comment 6 Martin Kosek 2014-03-19 08:39:33 UTC
ACK - this is perfect verification. Thanks!

Comment 7 Ludek Smid 2014-06-13 11:04:34 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.