[07:23] <boritek> hello, how can I fix/ignore a failed deployment state?
[12:31] <loomi> Does anyone know if it is possible to get an educational licence for the maas standard enterprise installation? If so where best to ask?
[13:30] <boritek> after a failed commissioning maas autocreated a dns entry for some reason, but that is not deletable from the gui
[13:30] <boritek> how can I get rid of it?
[14:12] <roaksoax> boritek: the dns entryh should expire
[14:12] <roaksoax> boritek: maas will always create dns entries for IP address it hands out
[14:40] <rzeigler> Is there anyone who has done virsh pods with maas that might be able to answer a question I have?
[14:44] <rzeigler> I'm not sure if I did something wrong when I set up the storage pool, but when I compose a machine and allocate the default 8G of disk, I end up with a logical volume that is 4Ms and then deployment fails because there isn't even enough space to write the filesystem.
[14:44] <rzeigler> At least I think that is what is happening
[14:49] <roaksoax> rzeigler: that's strange./ I've not seen that ever
[14:49] <rzeigler> so, I get
[14:50] <rzeigler> LV                                   VG   Attr       LSize Pool Origin                                         Data%  Meta%  Move Log Cpy%Sync Convert
[14:50] <rzeigler>   0a4f9552-e518-4d1a-8913-0b9cddef4fee maas swi-aos--- 4.00m      [0a4f9552-e518-4d1a-8913-0b9cddef4fee_vorigin] 0.00
[14:50] <rzeigler> out of lvs
[14:50] <rzeigler> when I lvresize upwards, I can successfully deploy
[14:51] <rzeigler> but that defeats the purpose of being able to use the dashboard
[14:53] <roaksoax> rzeigler: so you say your storage pool is inside LVM ?
[14:56] <rzeigler> I am using a volume group yes
[15:00] <roaksoax> rzeigler: could be related to that. If you can test against a non-LVM backed disk
[15:00] <roaksoax> rzeigler: vs a one that's backed
[15:00] <roaksoax> and things are different
[15:00] <roaksoax> could be an issue with that
[15:00] <rzeigler> oh
[15:00] <rzeigler> I think I misunderstood
[15:01] <rzeigler> so, I gave virsh a physical disk to make an lvm out of
[15:01] <rzeigler> and use as its pool
[15:05] <rzeigler> I think this may be an issue of misconfiguring libvirt
[15:05] <rzeigler> roaksoax: <allocation unit='bytes'>4194304</allocation> is in pool-dumpxml for my pool
[15:05] <rzeigler> which is about 4M
[15:12] <xygn4l> roaksoax: are Devices exposed via API? as in MAAS/#/devices
[15:12] <xygn4l> roaksoax: can they be created/configured/removed via the API
[15:14] <xygn4l> roaksoax: i see API commands for 'devices' so that might be it, but i also see *power* settings for 'devices'?  didnt think you managed power on Devices
[15:18] <boritek> roaksoax: what time should a dns entry expire? it does not seem to expire
[15:18] <boritek> i even retarted maas-controller host
[15:19] <xygn4l> dns does not expire.  did you mean dhcp?
[15:22] <boritek> no i mean DNS
[15:22] <boritek> roaksoax said it should expire
[15:23] <boritek> the ones that have been autocreated
[15:27] <xygn4l> are those machines no longer in maas?
[15:29] <boritek> xygn4l: no
[15:30] <boritek> there is only 1 deployed machine, all the others are only in ready state
[15:30] <boritek> and there is one that i cannot even commission for some reason
[15:32] <boritek> i said something couldnt reach BMC, but it could since, it can turn the machine on, then starts providioning, but it turns it off in the end and never turns it on again, until commissioning times out
[15:33] <boritek> i can also access it via ipmitool without any problem
[15:33] <roaksoax> they should autoexpire unless the dhcpd server is failing to tell maas to expire them
[15:33] <boritek> roaksoax: how much time does it need to expire?
[15:34] <roaksoax> boritek: the leases are every 6 minutes
[15:34] <roaksoax> iirc
[15:34] <boritek> if i turn off dhcp for a short time should it expire?
[15:34] <roaksoax> boritek: no
[15:34] <roaksoax> boritek: the dhcp server has a script that calls maas to "expire" IP's in the dynamic address which would remove the dns lease
[15:35] <boritek> How can i trigger this manually?
[15:36] <boritek> btw i have another problem i cannot set static IPs in the machine configs, because it says IP is already in use, which are not
[15:36] <roaksoax> boritek: sudo vim /var/lib/maas/dhcpd.conf see the bottom of that
[15:43] <boritek> roaksoax: /usr/sbin/maas-dhcp-helper notify --action expiry --mac ********* --ip-family ipv4 --ip xxxxxxxx
[15:43] <boritek> i issued that, but dns entry is still there
[15:56] <mup> Bug #1788430 opened: [2.5] Newly created VM's end up with "Error: Node must be connected to a network." <MAAS:Triaged> <https://launchpad.net/bugs/1788430>