#8959 Nightly test failure in test_integration/test_otp.py/TestOTPToken/test_check_otpd_after_idle_timeout
Closed: fixed 2 years ago by frenaud. Opened 2 years ago by mpolovka.

This is not a duplicate of #8940.

The test test_check_otpd_after_idle_timeout is failing in its setup phase with an error:

self = <ipatests.test_integration.test_otp.TestOTPToken object at 0x7f524757a240>

    @pytest.fixture
    def setup_otp_nsslapd(self):
        check_services = self.master.run_command(
            ['systemctl', 'list-units', '--state=failed']
        )
>       assert "0 loaded units listed" in check_services.stdout_text
E       assert '0 loaded units listed' in "  UNIT            LOAD   ACTIVE SUB    DESCRIPTION                  \n● network.service loaded failed failed LSB: Bri...Pass --all to see loaded but inactive units, too.\nTo show all installed unit files use 'systemctl list-unit-files'.\n"
E        +  where "  UNIT            LOAD   ACTIVE SUB    DESCRIPTION                  \n● network.service loaded failed failed LSB: Bri...Pass --all to see loaded but inactive units, too.\nTo show all installed unit files use 'systemctl list-unit-files'.\n" = <pytest_multihost.transport.SSHCommand object at 0x7f5247de2550>.stdout_text

test_integration/test_otp.py:300: AssertionError

Flo's investigation yields that the Vagrant image defines eth0 and eth1 interfaces, wherein eth1 fails initialization.

[testing_ipa-4.6] Nightly PR #1108 , report


Metadata Update from @frenaud:
- Issue tagged with: test-failure, tests

2 years ago

In fact, there's only one interface, but NetworkManager was failing, even before provisioning, with:

Oct 13 20:02:07 localhost NetworkManager[1720]: <info>  [1634155327.6596] ifcfg-rh: Ignoring connection /etc/sysconfig/network-scripts/ifcfg-eth1 (9c92fad9-6ecb-3e6
c-eb4d-8a47c6f50c04,"System eth1") due to NM_CONTROLLED=no. Unmanaged: interface-name:eth1.

That file exists on newer releases (e.g. Fedora 33), but for that vagrant box the content is:

#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
BOOTPROTO=dhcp
ONBOOT=yes
DEVICE=eth1
NM_CONTROLLED=no
#VAGRANT-END

While for Fedora 33 it is:

#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
BOOTPROTO=dhcp
ONBOOT=yes
DEVICE=eth1
NM_CONTROLLED=yes
#VAGRANT-END

I believe those files are left-overs of the image building process and they can be safely removed.

After deleting it and restarting the network service I was able to progress and finish the test (4 passed, 2 xfailed in 721.00 seconds).

I'm gonna try to build a new box, to see if the network service still complains. If that is not possible, because it's an old target, I'll try to fix the box and re-package it.

Metadata Update from @abiagion:
- Custom field on_review adjusted to https://github.com/freeipa/freeipa/pull/6069

2 years ago

ipa-4-6:

  • 101d01c ipatests: Update PR-CI template

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

2 years ago

Login to comment on this ticket.

Metadata