#9133 Nightly test failure in test_fips.py::TestInstallFIPS::test_basic
Closed: fixed 2 years ago by abbra. Opened 2 years ago by frenaud.

Issue

The test test_fips.py::TestInstallFIPS::test_basic is failing during the setup phase, see for instance PR #1599 with the following logs and report:

cls = <class 'ipatests.test_integration.test_fips.TestInstallFIPS'>
mh = <pytest_multihost.plugin.MultihostFixture object at 0x7f16f8260c40>

    @classmethod
    def install(cls, mh):
        super(TestInstallFIPS, cls).install(mh)
        # sanity check
        for host in cls.get_all_hosts():
            assert host.is_fips_mode
            assert fips.is_fips_enabled(host)
        # patch named-pkcs11 crypto policy
        # see RHBZ#1772111
        for host in [cls.master] + cls.replicas:
            host.run_command(
                [
                    "sed",
                    "-i",
                    "-E",
                    "s/RSAMD5;//g",
                    "/etc/crypto-policies/back-ends/bind.config",
                ]
            )
        # master with CA, KRA, DNS+DNSSEC
        tasks.install_master(cls.master, setup_dns=True, setup_kra=True)
        # replica with CA, KRA, DNS
>       tasks.install_replica(
            cls.master,
            cls.replicas[0],
            setup_dns=True,
            setup_ca=True,
            setup_kra=True,
        )

test_integration/test_fips.py:48: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
pytest_ipa/integration/tasks.py:473: in install_replica
    install_client(master, replica, extra_args=ntp_args,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

master = <ipatests.pytest_ipa.integration.host.Host master.ipa.test (master)>
client = <ipatests.pytest_ipa.integration.host.Host replica0.ipa.test (replica)>
extra_args = [], user = 'admin', password = 'Secret.123', unattended = True
stdin_text = None, nameservers = '192.168.122.73'

    def install_client(master, client, extra_args=[], user=None,
                       password=None, unattended=True, stdin_text=None,
                       nameservers='master'):
        """
        :param nameservers: nameservers to write in resolver config. Possible
               values:
               * "master" - use ip of `master` parameter
               * None - do not setup resolver
               * IP_ADDRESS or [IP_ADDRESS, ...] - use this address as resolver
        """
        apply_common_fixes(client)
        allow_sync_ptr(master)
        # Now, for the situations where a client resides in a different subnet from
        # master, we need to explicitly tell master to create a reverse zone for
        # the client and enable dynamic updates for this zone.
        zone, error = prepare_reverse_zone(master, client.ip)
        if not error:
            master.run_command(["ipa", "dnszone-mod", zone,
                                "--dynamic-update=TRUE"])
        if nameservers is not None:
            client.resolver.backup()
            if nameservers == 'master':
                nameservers = master.ip
            client.resolver.setup_resolver(nameservers, master.domain.name)
        if user is None:
            user = client.config.admin_name
        if password is None:
            password = client.config.admin_password

        args = [
            'ipa-client-install',
            '--domain', client.domain.name,
            '--realm', client.domain.realm,
            '-p', user,
            '-w', password,
            '--server', master.hostname
        ]

        if unattended:
            args.append('-U')

        args.extend(extra_args)

>       if is_fips_enabled(client) and 'ad' in master:
E       TypeError: argument of type 'Host' is not iterable

The regression was introduced with commit 5a42ab1.


Metadata Update from @abbra:
- Issue assigned to abbra

2 years ago

test failure seen in testing_master_latest PR 1600 Report

master:

  • 27ab216 ipatests: fix check for AD topology being present

ipa-4-9:

  • b6b5f60 ipatests: fix check for AD topology being present

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

2 years ago

Login to comment on this ticket.

Metadata