[07:40] <Xat`> hi guys
[07:43] <Xat`> anyone knows why I'm getting "Commissionning to failed commissionning", and in maas.log I have "Marking node failed: Node operation 'Commissioning' tmed out after 0:20:00"
[07:44] <Xat`> I tried to debug this during about 5 hours, unsuccessfully
[08:19] <Xat`> I have maas 1
[08:19] <Xat`> I have maas 1.7
[10:07] <mup> Bug #1519726 opened: Status ready but no RAM,  Asus node <MAAS:New> <https://launchpad.net/bugs/1519726>
[10:40] <mup> Bug #1519744 opened: code is showing in disk size field <MAAS:New> <https://launchpad.net/bugs/1519744>
[12:34] <mup> Bug #1519804 opened: get_by_pxealias() is not stable <MAAS:New> <https://launchpad.net/bugs/1519804>
[13:05] <mup> Bug #1519810 opened: cluser controller failing to detect interfaces on bootstrap <MAAS:New> <https://launchpad.net/bugs/1519810>
[13:14] <mup> Bug #1519810 changed: cluser controller failing to detect interfaces on bootstrap <MAAS:New> <https://launchpad.net/bugs/1519810>
[13:17] <mup> Bug #1519810 opened: cluser controller failing to detect interfaces on bootstrap <MAAS:New> <https://launchpad.net/bugs/1519810>
[13:41] <mup> Bug #1519828 opened: [1.9] Support for static routes <MAAS:New> <https://launchpad.net/bugs/1519828>
[14:02] <mup> Bug #1519832 opened: Proxing Region controller functions on Cluster controller <MAAS:New> <https://launchpad.net/bugs/1519832>
[14:05] <Xat`> is maas designed to deplay VM/OS ?
[14:05] <Xat`> deploy*
[16:13] <Xat`> guys how to use maas with vmware vm ?
[16:40] <LoRez> Xat`: Seems like you could script up a way to get vmware to create VMs that would network boot
[18:06] <Xat`> LoRez: can I use virsh with libvirt esx support ?
[18:38] <mup> Bug #1519744 changed: code is showing in disk size field <MAAS:New> <https://launchpad.net/bugs/1519744>
[18:48] <LoRez> Xat`: no clue.
[19:11] <mup> Bug #1519918 opened: "failed to detect a valid IP address" when trying to view node details <MAAS:Triaged> <MAAS 1.9:New> <MAAS trunk:Triaged> <https://launchpad.net/bugs/1519918>
[19:11] <mup> Bug #1519919 opened: MAAS Look for NIC with kernel module loaded and fall back doesn't check presistent device names <MAAS:New> <https://launchpad.net/bugs/1519919>
[20:12] <mup> Bug #1519936 opened: re-commissioning just to reset partition scheme is overkill <MAAS:New> <https://launchpad.net/bugs/1519936>
[20:27] <mup> Bug #1519936 changed: re-commissioning just to reset partition scheme is overkill <MAAS:New> <https://launchpad.net/bugs/1519936>
[20:30] <mup> Bug #1519936 opened: re-commissioning just to reset partition scheme is overkill <MAAS:New> <https://launchpad.net/bugs/1519936>
[20:42] <mup> Bug #1519936 changed: re-commissioning just to reset partition scheme is overkill <MAAS:Invalid> <https://launchpad.net/bugs/1519936>
[20:51] <mup> Bug #1519943 opened: Upgrade from 1.8 left stale devices in the UI? <MAAS:New> <https://launchpad.net/bugs/1519943>
[20:54] <mup> Bug #1519943 changed: Upgrade from 1.8 left stale devices in the UI? <MAAS:New> <https://launchpad.net/bugs/1519943>
[20:57] <mup> Bug #1519943 opened: Upgrade from 1.8 left stale devices in the UI? <MAAS:New> <https://launchpad.net/bugs/1519943>
[22:03] <mup> Bug #1519527 opened: 1.25.1 proposed:  lxc units all have the same IP address <openstack> <sts> <uosci> <juju-core:Triaged> <MAAS:Triaged by mpontillo> <MAAS 1.9:Triaged by mpontillo> <MAAS trunk:Triaged by mpontillo> <https://launchpad.net/bugs/1519527>