#7028 install-replica-install --setup-kra --setup-dns --setup-ca fails
Closed: invalid Opened by fbarreto.

Reproducible by test: TestInstallWithCA_DNS2

Install IPA server:

RUN ['ipa-server-install', '-n', 'ipa.test', '-r', 'IPA.TEST', '-p', 'Secret123', '-a', 'Secret123', '--domain-level=1', '-U', '--setup-dns', '--forwarder', '8.8.8.8', '--auto-reverse']

Install replica:

[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21] RUN ['ipa-replica-install', '-p', 'Secret123', '-w', 'Secret123', '-U', '--setup-ca', '--setup-kra', '--setup-dns', '--forwarder', '8.8.8.8', '--ip-address', '192.168.118.103', '-r', 'IPA.TEST']
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21] ipa         : ERROR    Could not resolve hostname replica2.ipa.test using DNS. Clients may not function properly. Please check your DNS setup. (Note that this check queries IPA DNS directly and ignores /etc/hosts.)
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21] ipa         : ERROR    There is no KRA server in the domain, can't setup a KRA clone
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21] WARNING: conflicting time&date synchronization service 'chronyd' will
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21] be disabled in favor of ntpd
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21]
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21] IPA client is already configured on this system, ignoring the --domain, --server, --realm, --hostname, --password and --keytab options.
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21] Your system may be partly configured.
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21] Run /usr/sbin/ipa-server-install --uninstall to clean up.
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21]
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21] ipa.ipapython.install.cli.install_tool(CompatServerReplicaInstall): ERROR    The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information
[ipa.ipatests.pytest_plugins.integration.host.Host.replica2.cmd21] Exit code: 3
FAILED
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> traceback >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
self = <ipatests.test_integration.test_installation.TestInstallWithCA_DNS2 object at 0x7f75827fcd10>
    @pytest.mark.skipif(config.domain_level == DOMAIN_LEVEL_0,
                        reason='does not work on DOMAIN_LEVEL_0 by design')
    def test_replica0_with_ca_kra_dns_install(self):
        super(
>           TestInstallWithCA_DNS2, self
        ).test_replica0_with_ca_kra_dns_install()
test_integration/test_installation.py:207:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
test_integration/test_installation.py:67: in test_replica0_with_ca_kra_dns_install
    setup_kra=True, setup_dns=True)
pytest_plugins/integration/tasks.py:393: in install_replica
    stdin_text=stdin_text)
../pytest_multihost/host.py:251: in run_command
    command.wait(raiseonerr=raiseonerr)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <pytest_multihost.transport.SSHCommand object at 0x7f758143dc90>, raiseonerr = True
    def wait(self, raiseonerr=True):
        """Wait for the remote process to exit
            Raises an excption if the exit code is not 0, unless raiseonerr is
            true.
            """
        if self._done:
            return self.returncode
        self._end_process()
        self._done = True
        if raiseonerr and self.returncode:
            self.log.error('Exit code: %s', self.returncode)
>           raise subprocess.CalledProcessError(self.returncode, self.argv)
E           CalledProcessError: Command '['ipa-replica-install', '-p', 'Secret123', '-w', 'Secret123', '-U', '--setup-ca', '--setup-kra', '--setup-dns', '--forwarder', '8.8.8.8', '--ip-address', '192.168.118.103', '-r', 'IPA.TEST']' returned non-zero exit status 3
../pytest_multihost/transport.py:159: CalledProcessError
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> entering PDB >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> /usr/lib/python2.7/site-packages/pytest_multihost/transport.py(159)wait()
-> raise subprocess.CalledProcessError(self.returncode, self.argv)
(Pdb) self.stderr_text
"ipa         : ERROR    Could not resolve hostname replica2.ipa.test using DNS. Clients may not function properly. Please check your DNS setup. (Note that this check queries IPA DNS directly and ignores /etc/hosts.)\nipa         : ERROR    There is no KRA server in the domain, can't setup a KRA clone\nipa.ipapython.install.cli.install_tool(CompatServerReplicaInstall): ERROR    The ipa-replica-install command failed. See /var/log/ipareplica-install.log for more information\n"

Entire log of the test (too long to paste here):
https://pastebin.com/fwRVecQF


This may be related to https://pagure.io/freeipa/issue/7013 and https://pagure.io/freeipa/issue/7008

This looks to me more like env setup issue (DNS) then #7041 therefore not closing as dup of #7013 (#7041)

Metadata Update from @pvoborni:
- Issue priority set to: critical
- Issue set to the milestone: FreeIPA 4.6

Metadata Update from @tkrizek:
- Issue set to the milestone: FreeIPA 4.6.1 (was: FreeIPA 4.6)

Metadata Update from @tkrizek:
- Issue set to the milestone: FreeIPA 4.6.2 (was: FreeIPA 4.6.1)

Metadata Update from @tdudlak:
- Issue set to the milestone: FreeIPA 4.6.3 (was: FreeIPA 4.6.2)

Hello, any update on this?

Metadata Update from @rcritten:
- Issue set to the milestone: FreeIPA 4.6.4 (was: FreeIPA 4.6.3)

FreeIPA 4.6.3 has been released, moving to FreeIPA 4.6.4 milestone

This is an env issue, not a real bug. Closing it

Metadata Update from @fbarreto:
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

Metadata