Our servers have 2 NICs connected to the maas network, eth0 and eth1 which should show on the UI,
Since upgrade to 1.9.1, I have been seeing systems all of a sudden showing the connection missing.
In the case of eth1, I am seeing these servers not showing the connection after commissioning.
In the case of eth0, it's the PXE NIC that loses the connection but it happens after the system has been commissioned. In that case, system will fail to deploy and remain in Allocated state. I have observed this for R720XD (screenshot attached) and SM15K servers.
The screen capture of this latest scenario shows system failing to deploy and remaining in Ready state. If system is allocated first, then it's in allocated state that it'll remain.
The error is "Node failed to be deployed, because of the following error: {"network": ["Node must be configured to use a network"]}"
From the event log, here's window where the issue seems to start:
Node changed status - From 'Releasing' to 'Ready' Tue, 26 Apr. 2016 00:56:09
Node changed status - From 'Allocated' to 'Releasing' Tue, 26 Apr. 2016 00:56:07
User releasing node - (oil-slave-9) Tue, 26 Apr. 2016 00:56:07
Node changed status - From 'Ready' to 'Allocated' (to oil-slave-9) Tue, 26 Apr. 2016 00:36:52
User acquiring node - (oil-slave-9) Tue, 26 Apr. 2016 00:36:52
Node powered off Mon, 25 Apr. 2016 21:18:56
Node changed status - From 'Releasing' to 'Ready' Mon, 25 Apr. 2016 21:18:55
Powering node off Mon, 25 Apr. 2016 21:18:45
Node changed status - From 'Failed deployment' to 'Releasing' Mon, 25 Apr. 2016 21:18:37
User releasing node - (oil-slave-13) Mon, 25 Apr. 2016 21:18:37
Node changed status - From 'Deploying' to 'Failed deployment' Mon, 25 Apr. 2016 20:42:49
TFTP Request - chain.c32 Mon, 25 Apr. 2016 20:12:08
PXE Request - local boot Mon, 25 Apr. 2016 20:12:08
TFTP Request - pxelinux.cfg/01-bc-30-5b-ee-aa-40 Mon, 25 Apr. 2016 20:12:08
TFTP Request - pxelinux.cfg/44454c4c-5800-1054-8042-b4c04f515631 Mon, 25 Apr. 2016 20:12:08
TFTP Request - pxelinux.0 Mon, 25 Apr. 2016 20:12:08
TFTP Request - pxelinux.0 Mon, 25 Apr. 2016 20:12:08
There's a failure lot Local boot at 20:12:08 then first failure to deploy happens at 00:36:52.
$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=====================================-================================-============-===============================================================================
ii maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server provisioning libraries
The maas logs (clusterd and regiond filtered for "2016-04-25 2[0|1|2|3] to "2016-04-26 00:[0|1|2|3]")