windows: networker tries to update invalid device and blocks machiner from working

[Bogdan Teleaga]

Logs here: http://sprunge.us/LdKN

This happens on the latest master as of now(b631875ff9ed67ec321f1d6fa90bc65d839b9e93), should probably be seen in the CI as well.

[Cheryl Jennings (cherylj)]

Error is:

machine-3: 2016-04-08 05:34:46 ERROR juju.worker.dependency engine.go:522 "machiner" manifold worker returned unexpected error: cannot update observed network config: cannot set link-layer devices to machine "3": invalid device "Loopback Pseudo-Interface 1": Name "Loopback Pseudo-Interface 1" not valid

[Cheryl Jennings (cherylj)]

The logs from the last CI run don't show this error:
http://data.vapour.ws/juju-ci/products/version-3869/maas-1_9-deploy-win2012hvr2-amd64/build-321/maas-1_9-deploy-win2012hvr2-amd64/machine-0/machine-0.log.gz

[Andrew McDermott (frobware)]

Reported via dellstack testing: https://bugs.launchpad.net/juju-core/+bug/1566791

[Bogdan Teleaga (bteleaga)]

Seen in the latest CI builds

http://data.vapour.ws/juju-ci/products/version-3881/maas-1_9-deploy-win2012hvr2-amd64/build-342/machine-1.log.gz

[Andrew McDermott (frobware)]

Can we attach the windows equivalent of /etc/network/interfaces? (I'm guessing there is such a thing.)

[Gabriel Samfira (gabriel-samfira)]

Hi Andrew,

There is no real equivalent to /etc/network/interfaces. Windows stores information about the system in various registry locations. The standard Windows way to get this kind of information is via WMI queries. For example, using powershell, to get a listing of network adapters:

Get-CimInstance -Class Win32_NetworkAdapter -Filter "PhysicalAdapter='True'"

To get a listing of all IP addresses configured on the system:

Get-CimInstance -Class MSFT_NetIPAddress -Namespace root/StandardCimv2

The net package seems to do a good job at listing interfaces and configured IP addresses though.

One note. Network interfaces in windows can have arbitrary names that even include spaces.

[Dimiter Naydenov (dimitern)]

Hey Gabriel,
Juju expects network interface names on Windows to be up to 255 characters, and spaces are ok. No other restrictions are imposed.
There are even tests with names like that.

Anyway, I'll look into it to see what's going on, and thanks to Cloudbase's guide I have a working win2012r2 to test on :)

[Dimiter Naydenov (dimitern)]

I see the root cause - since the bootstrap machine is on Ubuntu (where the API server and controller are), it cannot deal well with network config coming from a Windows machine. Fortunately, it should be easy to fix.

[Dimiter Naydenov (dimitern)]

Fix proposed: https://github.com/juju/juju/pull/5214