provisioningserver TestGetSourceAddress.test_returns_none_if_no_route_found sometimes fails locally

Bug #1989949 reported by Igor Brovtsin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Low
Unassigned

Bug Description

I tried running `make test` locally and the "provisioningserver.utils.tests.test_network.TestGetSourceAddress.test_returns_none_if_no_route_found" test failed with the following traceback on master/0d37f91f4dd233548fb78cde64823168e95caedb:

Traceback (most recent call last):
  File "/work/src/provisioningserver/utils/tests/test_network.py", line 2474, in test_returns_none_if_no_route_found
    self.assertThat(get_source_address("127.0.0.0"), Is(None))
  File "/work/.ve/lib/python3.10/site-packages/testtools/testcase.py", line 480, in assertThat
    raise mismatch_error
testtools.matchers._impl.MismatchError: '127.0.0.1' is not None

The environment is Ubuntu 22.04 LXD container.

Related branches

Alberto Donato (ack)
Changed in maas:
milestone: none → 3.3.0
status: New → Triaged
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
milestone: 3.3.0 → 3.3.0-beta1
Changed in maas:
status: Fix Committed → Fix Released
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.