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 1435397 - ipa-replica-install can't install replica file produced by ipa-replica-prepare on 4.5
Summary: ipa-replica-install can't install replica file produced by ipa-replica-prepar...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Nikhil Dehadrai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-23 17:31 UTC by Petr Vobornik
Modified: 2017-08-01 09:46 UTC (History)
6 users (show)

Fixed In Version: ipa-4.5.0-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 09:46:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2304 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2017-08-01 12:41:35 UTC

Description Petr Vobornik 2017-03-23 17:31:20 UTC 
Cloned from upstream: https://pagure.io/freeipa/issue/6777

ipa-replica-install fails with:

```
  [14/22]: publish CA cert
  [error] CalledProcessError: Command '/usr/bin/certutil -d /etc/httpd/alias -L -n ABC.IDM.LAB.ENG.BRQ.REDHAT.COM IPA CA -a -f /etc/httpd/alias/pwdfile.txt' returned non-zero exit status 255
Your system may be partly configured.
Run /usr/sbin/ipa-server-install --uninstall to clean up.

ipa.ipapython.install.cli.install_tool(CompatServerReplicaInstall): ERROR    Command '/usr/bin/certutil -d /etc/httpd/alias -L -n ABC.IDM.LAB.ENG.BRQ.REDHAT.COM IPA CA -a -f /etc/httpd/alias/pwdfile.txt' returned non-zero exit status 255
ipa.ipapython.install.cli.install_tool(CompatServerReplicaInstall): ERROR    The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
```
Comment 2 Petr Vobornik 2017-03-23 17:31:35 UTC 
Upstream ticket:
https://pagure.io/freeipa/issue/6777
Comment 3 Petr Vobornik 2017-03-23 17:32:27 UTC 
master:

    9939aa53630a9c6a66e83140e64ec56539891c13 replica prepare: fix wrong IPA CA nickname in replica file

ipa-4-5:

    df60e88e1bca6efd5ebf2a88e7825a5fd2631f08 replica prepare: fix wrong IPA CA nickname in replica file
Comment 5 Nikhil Dehadrai 2017-06-06 10:44:43 UTC 
IPA-versions:
1) RHEL 7.1.z : ipa-server-4.1.0-18.el7_1.4.x86_64
2) RHEL 7.2.z : ipa-server-4.2.0-15.el7_2.19.x86_64
REPLICA-Versions: ipa-server-4.5.0-14.el7.x86_64

1. Verified that ipa-replica install command run successfully when replica file is produced by ipa-replica-prepare from IPA-MASTER (In my case RHEL 7.1.z, RHEL 7.2.z).
2. Refer the console output below:

7.1.z:
=======

MASTER:
--------
[root@bkr-hv03-guest31 ipa]# rpm -q ipa-server
ipa-server-4.1.0-18.el7_1.4.x86_64
[root@bkr-hv03-guest31 ipa]# ipa-replica-manage list
bkr-hv03-guest31.testrelm.test: master
auto-hv-02-guest01.testrelm.test: master

REPLICA:
--------
[root@auto-hv-02-guest01 ipa]# rpm -q ipa-server
ipa-server-4.5.0-14.el7.x86_64
[root@auto-hv-02-guest01 ipa]# kinit admin
Password for admin: 
[root@auto-hv-02-guest01 ipa]# rpm -q selinux-policy
selinux-policy-3.13.1-159.el7.noarch
[root@auto-hv-02-guest01 ipa]# grep -rn "CalledProcessError" /var/log/ipareplica-install.log 
[root@auto-hv-02-guest01 ipa]# grep -rn "CompatServerReplicaInstall" /var/log/ipareplica-install.log
[root@auto-hv-02-guest01 ipa]# tail -1 /var/log/ipareplica-install.log
2017-06-06T10:18:44Z INFO The ipa-replica-install command was successful


7.2.z:
========

MASTER:
--------
[root@bkr-hv03-guest06 ipa]# rpm -q ipa-server
ipa-server-4.2.0-15.el7_2.19.x86_64
[root@bkr-hv03-guest06 ipa]# ipa-replica-manage list
bkr-hv03-guest06.testrelm.test: master
ipaqavmh.testrelm.test: master

REPLICA:
--------
[root@ipaqavmh ipa]# rpm -q ipa-server
ipa-server-4.5.0-14.el7.x86_64
[root@ipaqavmh ipa]# kinit admin
Password for admin: 
[root@ipaqavmh ipa]# grep -rn "CalledProcessError" /var/log/ipareplica-install.log
[root@ipaqavmh ipa]# grep -rn "CompatServerReplicaInstall" /var/log/ipareplica-install.log
[root@ipaqavmh ipa]# tail -1 /var/log/ipareplica-install.log 
2017-06-06T10:09:51Z INFO The ipa-replica-install command was successful

3) For REPLICA install against IPA-MASTER configured at v3 (RHEL 6.9.z), there is a separate bug bz#1434910

Thus on the basis of above observations marking status of bug to "VERIFIED"
Comment 6 errata-xmlrpc 2017-08-01 09:46:16 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, 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/RHBA-2017:2304
Note You need to log in before you can comment on or make changes to this bug.