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.
Description of problem: Replica installation fails with latest ipa-container image Version-Release number of selected component (if applicable): image: ipa-server-container-4.6.4-28 Atomic host: Version: 7.6.6 (2019-07-24 08:47:27) How reproducible: Always Steps to Reproduce: 1. Setup Atomic host at latest version for Master and replica and download ipa-container image to it using curl command. 2. Setup ipa-server using latest ipa-container image # atomic install --name ipadocker rhel7/ipa-server net-host --hostname=`hostname` --setup-dns --ip-address=10.x.x.x --forwarder=10.x.x.x -r NDTEST766.TEST -a Secret123 -p Secret123 --no-ntp -U 3. Setup ipa-replica against this ipa-master # atomic install --name replicadocker rhel7/ipa-server net-host ipa-replica-install --setup-dns --setup-ca --server=master.ndtest766.test --domain ndtest766.test --forwarder=10.x.x.x --admin-password Secret123 --principal admin -U Actual results: ipa-replica installation FAILS [root@nikhil-atomic-host-7 ~]# atomic install --name replicadocker rhel7/ipa-server net-host ipa-replica-install --setup-dns --setup-ca --server=master.ndtest766.test --domain ndtest766.test --forwarder=10.x.x.x --admin-password Secret123 --principal admin -U docker run -ti --rm --privileged -v /:/host -e HOST=/host -e DATADIR=/var/lib/replicadocker -e NAME=replicadocker -e IMAGE=rhel7/ipa-server rhel7/ipa-server /bin/install.sh net-host ipa-replica-install --setup-dns --setup-ca --server=master.ndtest766.test --domain ndtest766.test --forwarder=10.x.x.x --admin-password Secret123 --principal admin -U + chroot /host /usr/bin/docker run -ti --rm --name replicadocker -e NAME=replicadocker -e IMAGE=rhel7/ipa-server -v /var/lib/replicadocker:/data:Z -v /sys/fs/cgroup:/sys/fs/cgroup:ro -v /dev/urandom:/dev/random:ro --tmpfs /run --tmpfs /tmp --net=host rhel7/ipa-server exit-on-finished ipa-replica-install --setup-dns --setup-ca --server=master.ndtest766.test --domain ndtest766.test --forwarder=10.x.x.x --admin-password Secret123 --principal admin -U systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN) Detected virtualization other. Detected architecture x86-64. Set hostname to <replica.ndtest766.test>. Thu Jul 25 15:46:26 UTC 2019 /usr/sbin/ipa-server-configure-first Configuring client side components Client hostname: replica.ndtest766.test Realm: NDTEST766.TEST DNS Domain: ndtest766.test IPA Server: master.ndtest766.test BaseDN: dc=ndtest766,dc=test Skipping synchronizing time with NTP server. Successfully retrieved CA cert Subject: CN=Certificate Authority,O=NDTEST766.TEST Issuer: CN=Certificate Authority,O=NDTEST766.TEST Valid From: 2019-07-25 15:01:51 Valid Until: 2039-07-25 15:01:51 Enrolled in IPA realm NDTEST766.TEST Created /etc/ipa/default.conf New SSSD config will be created Configured sudoers in /data/etc/nsswitch.conf Configured /etc/sssd/sssd.conf Configured /etc/krb5.conf for IPA realm NDTEST766.TEST trying https://master.ndtest766.test/ipa/json [try 1]: Forwarding 'schema' to json server 'https://master.ndtest766.test/ipa/json' trying https://master.ndtest766.test/ipa/session/json [try 1]: Forwarding 'ping' to json server 'https://master.ndtest766.test/ipa/session/json' [try 1]: Forwarding 'ca_is_enabled' to json server 'https://master.ndtest766.test/ipa/session/json' Systemwide CA database updated. Hostname (replica.ndtest766.test) does not have A/AAAA record. Failed to update DNS records. Missing A/AAAA record(s) for host replica.ndtest766.test: 10.x.x.x. Incorrect reverse record(s): 10.x.x.x is pointing to ci-vm-10-0-149-211.hosted.upshift.rdu2.redhat.com. instead of replica.ndtest766.test. SSSD enabled Configured /etc/openldap/ldap.conf /etc/ssh/ssh_config not found, skipping configuration /etc/ssh/sshd_config not found, skipping configuration Configuring ndtest766.test as NIS domain. Client configuration complete. The ipa-client-install command was successful ipaserver.install.server.replicainstall: ERROR The IP address 10.x.x.x of host master.ndtest766.test resolves to: ci-vm-10-0-x-x.hosted.upshift.rdu2.redhat.com.. Clients may not function properly. Please check your DNS setup. (Note that this check queries IPA DNS directly and ignores /etc/hosts.) Checking DNS forwarders, please wait ... Run connection check to master Connection check OK Configuring NTP daemon (ntpd) [1/4]: stopping ntpd [2/4]: writing configuration [3/4]: configuring ntpd to start on boot [4/4]: starting ntpd Done configuring NTP daemon (ntpd). Configuring directory server (dirsrv). Estimated time: 30 seconds [1/41]: creating directory server instance [2/41]: enabling ldapi [3/41]: configure autobind for root [4/41]: stopping directory server [5/41]: updating configuration in dse.ldif [6/41]: starting directory server [7/41]: adding default schema [8/41]: enabling memberof plugin [9/41]: enabling winsync plugin [10/41]: configuring replication version plugin [11/41]: enabling IPA enrollment plugin [12/41]: configuring uniqueness plugin [13/41]: configuring uuid plugin [14/41]: configuring modrdn plugin [15/41]: configuring DNS plugin [16/41]: enabling entryUSN plugin [17/41]: configuring lockout plugin [18/41]: configuring topology plugin [19/41]: creating indices [20/41]: enabling referential integrity plugin [21/41]: configuring certmap.conf [22/41]: configure new location for managed entries [23/41]: configure dirsrv ccache [24/41]: enabling SASL mapping fallback [25/41]: restarting directory server [26/41]: creating DS keytab [27/41]: ignore time skew for initial replication [28/41]: setting up initial replication Starting replication, please wait until this has completed. Update in progress, 4 seconds elapsed Update succeeded [29/41]: prevent time skew after initial replication [30/41]: adding sasl mappings to the directory [31/41]: updating schema [32/41]: setting Auto Member configuration [33/41]: enabling S4U2Proxy delegation [34/41]: initializing group membership [35/41]: adding master entry [36/41]: initializing domain level [37/41]: configuring Posix uid/gid generation [38/41]: adding replication acis [39/41]: activating sidgen plugin [40/41]: activating extdom plugin [41/41]: configuring directory to start on boot Done configuring directory server (dirsrv). Configuring Kerberos KDC (krb5kdc) [1/5]: configuring KDC [2/5]: adding the password extension to the directory [3/5]: creating anonymous principal [4/5]: starting the KDC [5/5]: configuring KDC to start on boot Done configuring Kerberos KDC (krb5kdc). Configuring kadmin [1/2]: starting kadmin [2/2]: configuring kadmin to start on boot Done configuring kadmin. Configuring directory server (dirsrv) [1/3]: configuring TLS for DS instance [2/3]: importing CA certificates from LDAP [3/3]: restarting directory server Done configuring directory server (dirsrv). Configuring the web interface (httpd) [1/22]: stopping httpd [2/22]: setting mod_nss port to 443 [3/22]: setting mod_nss cipher suite [4/22]: setting mod_nss protocol list to TLSv1.0 - TLSv1.2 [5/22]: setting mod_nss password file [6/22]: enabling mod_nss renegotiate [7/22]: disabling mod_nss OCSP [8/22]: adding URL rewriting rules [9/22]: configuring httpd [10/22]: setting up httpd keytab [11/22]: configuring Gssproxy [12/22]: setting up ssl [13/22]: configure certmonger for renewals [14/22]: importing CA certificates from LDAP [15/22]: publish CA cert [16/22]: clean up any existing httpd ccaches [17/22]: configuring SELinux for httpd [18/22]: create KDC proxy config [19/22]: enable KDC proxy [20/22]: starting httpd [21/22]: configuring httpd to start on boot [22/22]: enabling oddjobd Done configuring the web interface (httpd). Configuring ipa-otpd [1/2]: starting ipa-otpd [2/2]: configuring ipa-otpd to start on boot Done configuring ipa-otpd. Configuring ipa-custodia [1/4]: Generating ipa-custodia config file [2/4]: Generating ipa-custodia keys [3/4]: starting ipa-custodia [4/4]: configuring ipa-custodia to start on boot Done configuring ipa-custodia. Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes [1/28]: creating certificate server db [2/28]: setting up initial replication Starting replication, please wait until this has completed. Update in progress, 4 seconds elapsed Update succeeded [3/28]: creating ACIs for admin [4/28]: creating installation admin user [5/28]: configuring certificate server instance [6/28]: exporting Dogtag certificate store pin [7/28]: stopping certificate server instance to update CS.cfg [8/28]: backing up CS.cfg [9/28]: disabling nonces [10/28]: set up CRL publishing [11/28]: enable PKIX certificate path discovery and validation [12/28]: destroying installation admin user [13/28]: starting certificate server instance [14/28]: Finalize replication settings [15/28]: configure certmonger for renewals [16/28]: Importing RA key xargs: /usr/sbin/ipa-replica-install: terminated by signal 9 FreeIPA server configuration failed. Expected results: ipa-replica installation is successful