Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1075129
Description of problem: This i faced when i tried to create a replica from a Replica (RHEL-7.0) which was migrated from a RHEL-6.5 based Master. Version-Release number of selected component (if applicable): [root@rhel70-replica ~]# rpm -q ipa-server pki-ca 389-ds-base ipa-server-3.3.3-21.el7.x86_64 pki-ca-10.0.5-3.el7.noarch 389-ds-base-1.3.1.6-22.el7.x86_64 [root@rhel70-replica ~]# How reproducible: Always Steps to Reproduce: 1. Install Master on RHEL-6.5 2. Install Replica on RHEL-7.0 from RHEL-6.5 based Master. 3. Now again install another replica on RHEL-7.0 from replica of step (2). Actual results: Bogus time estimate shown for configuration of various component (dirsrv, ca instance etc) Expected results: No bogus time estimate should be shown. ======================================================================== Here directory server configuration show that it will take 31 minutes but actually it takes less than that. Configuring directory server (dirsrv): Estimated time 31 minutes [1/34]: creating directory server user [2/34]: creating directory server instance [3/34]: adding default schema [4/34]: enabling memberof plugin [5/34]: enabling winsync plugin [6/34]: configuring replication version plugin [7/34]: enabling IPA enrollment plugin [8/34]: enabling ldapi [9/34]: configuring uniqueness plugin [10/34]: configuring uuid plugin [11/34]: configuring modrdn plugin [12/34]: configuring DNS plugin [13/34]: enabling entryUSN plugin [14/34]: configuring lockout plugin [15/34]: creating indices [16/34]: enabling referential integrity plugin [17/34]: configuring ssl for ds instance [18/34]: configuring certmap.conf [19/34]: configure autobind for root [20/34]: configure new location for managed entries [21/34]: configure dirsrv ccache [22/34]: enable SASL mapping fallback [23/34]: restarting directory server [24/34]: setting up initial replication Starting replication, please wait until this has completed. Update in progress, 21 seconds elapsed Update succeeded [25/34]: updating schema [26/34]: setting Auto Member configuration [27/34]: enabling S4U2Proxy delegation [28/34]: initializing group membership [29/34]: adding master entry [30/34]: configuring Posix uid/gid generation [31/34]: adding replication acis [32/34]: enabling compatibility plugin [33/34]: tuning directory server [34/34]: configuring directory to start on boot Done configuring directory server (dirsrv). Configuring certificate server (pki-tomcatd): Estimated time 33 minutes 30 seconds [1/19]: creating certificate server user [2/19]: configuring certificate server instance ipa : CRITICAL failed to configure ca instance Command '/usr/sbin/pkispawn -s CA -f /tmp/tmp8ZctZ3' returned non-zero exit status 1 Your system may be partly configured.
This is probably caused by the strange way of process the time duration in seconds:
... if runtime > 0: plural='' est = time.localtime(runtime) ...
Petr is looking at it, it should be a very short fix.
master:
Metadata Update from @dpal: - Issue assigned to pviktori - Issue set to the milestone: FreeIPA 4.0 - 2014/03
Login to comment on this ticket.