Canonical Juju

container networking broken in GCE

Bug #1675546 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Christian Muirhead
Canonical Juju 2.2-beta1

Bug Description

As of commit
     https://github.com/juju/juju/commit/565ce69fc1b98f5e6e4bb68ae10734a0730b2f4f

The GCE tests that use containers
    http://juju-ci.vapour.ws/job/gce-deployer-bundle
    http://juju-ci.vapour.ws/job/gce-bundle-lxd

Fail to bring up any containers. The tests timeout waiting for lxd to start and agents to call home.

Revision history for this message
Christian Muirhead (2-xtian) wrote :

environ.NetworkInterfaces doesn't work for legacy networks (which the juju-qa account uses) - in that case the interface coming back has "" for the subnet. I'm fixing it to get the relevant details from the network when there's no subnetwork linked.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

PR against develop (2.2): https://github.com/juju/juju/pull/7150

Changed in juju:
status: Triaged → In Progress
Christian Muirhead (2-xtian)
Changed in juju:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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