Spurious failure in test_get_hostname_ip_mapping_returns_fqdn_and_other

Bug #1602848 reported by Gavin Panella
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Unassigned

Bug Description

Seen when landing a branch to lp:maas/2.0:

FAIL: maasserver.models.tests.test_staticipaddress.TestStaticIPAddressManagerMapping.test_get_hostname_ip_mapping_returns_fqdn_and_other
----------------------------------------------------------------------
testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/tmp/tarmac/branch.nsyM9g/src/maastesting/runtest.py", line 135, in _run_user
    result = function(*args, **kwargs)
  File "/home/ubuntu/.buildout/eggs/testtools-2.1.0-py3.5.egg/testtools/testcase.py", line 714, in _run_test_method
    return self._get_test_method()()
  File "/tmp/tarmac/branch.nsyM9g/src/maasserver/models/tests/test_staticipaddress.py", line 408, in test_get_hostname_ip_mapping_returns_fqdn_and_other
    }, mapping)
  File "/home/ubuntu/.buildout/eggs/testtools-2.1.0-py3.5.egg/testtools/testcase.py", line 406, in assertEqual
    self.assertThat(observed, matcher, message)
  File "/home/ubuntu/.buildout/eggs/testtools-2.1.0-py3.5.egg/testtools/testcase.py", line 493, in assertThat
    raise mismatch_error
testtools.matchers._impl.MismatchError: !=:
reference = {'eth-h5Nh8S.hostname-xAUGgm.domain-vZIpct': HostnameIPMapping('4y3h7n', 30, {'60.174.134.104'}, 0),
 'hostname-xAUGgm.domain-vZIpct': HostnameIPMapping('4y3h7n', 30, {'60.174.134.107'}, 0)}
actual = defaultdict(<class 'maasserver.models.staticipaddress.HostnameIPMapping'>,
            {'eth-h5Nh8S.hostname-xAUGgm.domain-vZIpct': HostnameIPMapping('4y3h7n', 30, {'60.174.134.107'}, 0),
             'hostname-xAUGgm.domain-vZIpct': HostnameIPMapping('4y3h7n', 30, {'60.174.134.104'}, 0)})

Tags: tests
Revision history for this message
LaMont Jones (lamont) wrote :

in 125 iterations, 12 failures.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi!

**This is an automated message**

We believe this is may no longer be an issue in the latest MAAS release. Due to the report date of this, we are currently marking it as Invalid. If you believe this bug report still valid against the latest release of MAAS, or if you are still interested in this, please re-open this bug report.

Thanks

Changed in maas:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.