provider/maas: test failure because of test isolation failure

Bug #1516036 reported by Roger Peppe
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Medium
Andrew McDermott
1.25
Fix Released
Medium
Andrew McDermott

Bug Description

instanceTest.TestAddresses and instanceTest.TestAddressesMissing both fail on my machine
because inst.Addresses calls network.ResolvableHostnames and my IP provider successfully
resolves any IP address, including "testing.invalid".

--- FAIL: TestMAAS (0.06s)
FAIL: instance_test.go:51: instanceTest.TestAddresses

[LOG] 0:00.000 DEBUG juju.testing setting feature flags: address-allocation
instance_test.go:68:
    c.Check(addr, gc.DeepEquals, expected)
... obtained []network.Address = []network.Address{public:testing.invalid, local-cloud:testing.invalid, public:1.2.3.4, link-local:fe80::d806:dbff:fe23:1199}
... expected []network.Address = []network.Address{public:1.2.3.4, link-local:fe80::d806:dbff:fe23:1199}

----------------------------------------------------------------------
FAIL: instance_test.go:71: instanceTest.TestAddressesMissing

[LOG] 0:00.000 DEBUG juju.testing setting feature flags: address-allocation
instance_test.go:83:
    c.Check(addr, gc.DeepEquals, []network.Address{})
... obtained []network.Address = []network.Address{public:testing.invalid, local-cloud:testing.invalid}
... expected []network.Address = []network.Address{}

exit status 1

Tags: 2.0-count
Revision history for this message
Andrew McDermott (frobware) wrote :

I tested this with 8.8.8.8 as my provider and it doesn't, though I see that my ISPs resolver does.

Revision history for this message
Andrew McDermott (frobware) wrote :

If you're currently blocked by this could you change your host to use 8.8.8.8 as a resolver?

Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Andrew McDermott (frobware) wrote :

Quick patch - needs verification this is the direction we want, but passes when I use my ISPs resolver. Without the patch, and with my ISPs revolver, it fails.

Revision history for this message
Andrew McDermott (frobware) wrote :
Changed in juju-core:
assignee: nobody → Andrew McDermott (frobware)
Changed in juju-core:
status: Triaged → In Progress
Changed in juju-core:
status: In Progress → Fix Committed
Changed in juju-core:
milestone: none → 1.25.1
milestone: 1.25.1 → none
Revision history for this message
Andrew McDermott (frobware) wrote :

Based on some discussions with mgz and dimitern I am going to rework this.

From IRC:

<mgz> the tests actually query a real dns server, so the solution is changing the value that escapes testing to fail more, rather than correctly isolating the tests from the runner's dns setup?

Changed in juju-core:
status: Fix Committed → In Progress
Revision history for this message
Andrew McDermott (frobware) wrote :

RB for 1.25 - http://reviews.vapour.ws/r/3327/

Assuming that's OK then I will revert the original "fix" on master (commit 8a3d71c3aaf12ce80ca84bceb6c87013ae7e584e) and forward port this fix from 1.25 to master.

Changed in juju-core:
milestone: none → 1.25.3
milestone: 1.25.3 → none
Revision history for this message
Andrew McDermott (frobware) wrote :
Changed in juju-core:
status: In Progress → Fix Committed
Changed in juju-core:
milestone: none → 2.0-alpha1
Changed in juju-core:
milestone: 2.0-alpha1 → 1.26-alpha3
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
tags: added: 2.0-count
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.