Composing a VM with an IP address on its interface is in Auto Assign state after commissioning

[Nicolas Pochet]

When composing a VM with an IP address on its interface with the following command:

maas root pod compose 5 hostname=foo cores=1 memory=1024 storage=5 interfaces="eth0:space=oam-space,ip=192.168.105.10"

results in the VM having its interface in Auto Assign mode after commissioning.

I also tried with:
maas root pod compose 5 hostname=foo cores=1 memory=1024 storage=5 interfaces="eth0:space=oam-space,ip=192.168.105.10,mode=static"

But the result is the same.

The expected result would be that the VM has an IP address that persist after commissioning.

[Vern Hart (vern)]

I tried this on maas 2.6.2 and verified that the node commissions with the given static ip, the mode is auto and the ip goes away after it finishes commissioning.

ubuntu@OrangeBox100:~$ maas admin pod compose 13 hostname=vern1 cores=1 memory=1024 storage=5 interfaces="eth0:space=undefined,ip=172.27.100.100,mode=static"
Success.
Machine-readable output follows:
{
    "system_id": "73a8gy",
    "resource_uri": "/MAAS/api/2.0/machines/73a8gy/"
}
ubuntu@OrangeBox100:~$ systemid=73a8gy
ubuntu@OrangeBox100:~$ maas admin machine read $systemid | jq '{"status": .status_name, "boot_interface": .boot_interface.links[0] | {"mode": .mode, "ip_address": .ip_address}}'
{
  "status": "Commissioning",
  "boot_interface": {
    "mode": "auto",
    "ip_address": "172.27.100.100"
  }
}
ubuntu@OrangeBox100:~$ maas admin machine read $systemid | jq '{"status": .status_name, "boot_interface": .boot_interface.links[0] | {"mode": .mode, "ip_address": .ip_address}}'
{
  "status": "Ready",
  "boot_interface": {
    "mode": "auto",
    "ip_address": null
  }
}
ubuntu@OrangeBox100:~$ maas admin version read
Success.
Machine-readable output follows:
{"capabilities": ["networks-management", "static-ipaddresses", "ipv6-deployment-ubuntu", "devices-management", "storage-deployment-ubuntu", "network-deployment-ubuntu", "bridging-interface-ubuntu", "bridging-automatic-ubuntu", "authenticate-api"], "version": "2.6.2", "subversion": "7841-ga10625be3-0ubuntu1~19.10.1"}

[Andre Ruiz (andre-ruiz)]

I'm having this problem right now with maas snap 2.9.2.

I'm using "eth0:space=oam:ip=x.x.x.x" (as opposed to "eth0:space=oam,ip=x.x.x.x) but I don't think this makes a difference because the behavior I see is exactly the same as described (ip gets assigned, can be seen in the network config screen but after commissioning it goes away).

We are not blocked by this right now because static ip is not necessary in initial tests but it will become a problem soon.

[Andre Ruiz (andre-ruiz)]

Just mentioning that https://bugs.launchpad.net/maas/+bug/1883349 is a duplicate of this and there it mentions a workaround.

[Björn Tillenius (bjornt)]

The issue here is that after composing the VM, we do a normal commissioning of the VM. That will autodetect the interface configuration and reset them to the default configuration, which is auto assign.

Given that we configure the interfaces fully on compose, we can probably get away with setting retain_network_configuration to True.

Or we could store the composed network configuration and use that when configuring networking after commissioning.

[Thorsten Merten (thorsten-merten)]

When commissioning, the machine might have an IP assigned from an IP range reserved for commissioning and ephemeral tasks. These IPs are not supposed to be re-used for machines (VMs) that are ready/new. To me this seems to be by design and thus the bug is invalid.
We will be redesigning a lot of networking and I will make sure that this will be linked to our PF board as one part of the discussion