network_get() missing information

Bug #1818359 reported by james beedy on 2019-03-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Joseph Phillips

Bug Description

Network_get() only returns a subset of the information.

Pretty sure I'm only seeing this on the `localhost` provider.


To replicate, using the localhost provider run:

juju deploy kubernetes-core
juju run --application kubernetes-worker "network-get cni"

John A Meinel (jameinel) wrote :

This seems like the Machiner isn't properly inventorying the network interfaces when bootstrapping with LXD. Which seems surprising, and seems worth investigating.

Changed in juju:
status: New → Triaged
assignee: nobody → Joseph Phillips (manadart)
importance: Undecided → High
Joseph Phillips (manadart) wrote :

Looks like the machiner is populating link-layer devices correctly.
It is particular to `network-get` for the LXD provider.

Investigation ongoing.

Joseph Phillips (manadart) wrote :

This will occur for providers that do not support subnet discovery.

Subnet discovery works on these providers:
- gce
- ec2
- maas
- openstack
- oci
- oracle (to be deprecated)

We will see this on the others.

We are currently in the midst of significant work on the Juju networking model where we intend to make the networking experience consistent across providers, including mutable spaces for all. This will be rectified as part of that work.

Changed in juju:
milestone: none → 2.7.4
Changed in juju:
status: Triaged → Fix Committed
Changed in juju:
milestone: 2.7.4 → 2.7.5
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers