=== bradm_ is now known as bradm
=== jgrassle1 is now known as jgrassler
=== ikonia_ is now known as ikonia
[11:10] <mup> Bug #1567176 changed: [2.0b1] django.db.utils.IntegrityError: duplicate key value violates unique constraint "maasserver_space_pkey" <MAAS:Invalid> <https://launchpad.net/bugs/1567176>
[11:19] <mup> Bug #1567176 opened: [2.0b1] django.db.utils.IntegrityError: duplicate key value violates unique constraint "maasserver_space_pkey" <MAAS:Invalid> <https://launchpad.net/bugs/1567176>
[11:22] <mup> Bug #1567176 changed: [2.0b1] django.db.utils.IntegrityError: duplicate key value violates unique constraint "maasserver_space_pkey" <MAAS:Invalid> <https://launchpad.net/bugs/1567176>
[12:59] <mup> Bug #1660743 changed: [2.1.3] When commissioning a 'NEW' machine from the Machine details page, it incorrectly shows 'MAAS is not providing DHCP.' message <maas-at-home> <oil> <MAAS:Invalid> <MAAS 2.1:Won't Fix> <https://launchpad.net/bugs/1660743>
[12:59] <mup> Bug #1681611 changed: Page must be refreshed when scripts updated via the API/CLI <MAAS:Fix Released by ltrager> <https://launchpad.net/bugs/1681611>
[16:02] <xygnal> does PXE mode auto-clear when a node reaches deployed state?I noticed a problem with my curtin late command to turn off PXE, and only just fixed it now.
[16:02] <xygnal> need to understand if I need to go through those other nodes and manually clear that to avoid re-builds
[16:08] <mup> Bug #1699222 opened: [2.2] Updateing virsh power parameters for one node affects other node <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1699222>
[16:27] <roaksoax_> xygnal: howdy! maas only tells the BMC to PXE boot on next boot
[16:30] <roaksoax_> xygnal: so uf the machine's bios is set to pxe boot, on reboot it should pxe
[16:30] <roaksoax_> xygnal: if the machine is set to boot from disk, on reboot it should just boot from disk
[16:31] <roaksoax_> in EFI is the same behavior, although, there was a bug in curtin that if maas wasn't available, it wouldn't boot from local disk
[16:31] <xygnal> how do you avoid an accidental PXE causing it to re-deploy?
[16:31] <roaksoax_> xygnal: if the machine is 'deployed' maas will tell it to localboot if the machines PXE's
=== roaksoax_ is now known as roaksoax
[16:31] <xygnal> ok that was what I was looking for, confirmation that once deployed status it will respond differentl
[16:32] <xygnal> the problem was that the statement telling it to not pxe boot during DEPLOYING was not triggering, so it would just continue to re-pxe deploy :)
[16:42] <roaksoax> xygnal: yeah maas should never tell the machine to re-deploy when it is already deployed
[17:47] <mup> Bug #1699286 opened: [2.2, trunk] test__renders_ntp_servers_as_comma_separated_list fails randomly <MAAS:Triaged by mpontillo> <MAAS 2.2:Triaged by mpontillo> <https://launchpad.net/bugs/1699286>
[18:32] <mup> Bug #1605312 changed: Unhandled failure in updating lease. django.db.utils.IntegrityError: duplicate key value violates unique constraint "maasserver_staticipaddress_ip_key" <MAAS:Invalid> <https://launchpad.net/bugs/1605312>
[19:11] <mup> Bug #1699308 opened: [2.2] TestDeviceHandler.test_list_num_queries_is_the_expected_number fails randomly <MAAS:New> <https://launchpad.net/bugs/1699308>
[19:52] <xygnal> anyone tried to deply esxi using maas? i know its unsupported.  curious if anyone has tried.
[20:07] <ikonia> actually deploy esx, or deploy to esx
[22:17] <seanhoughton> hi all, we're using MaaS to provision KVM vms but on our production server we get an error "No user data registered for node named ct-vm-01001" just after the node transitions to DEPLOYED state. I've looked through the code but it's getting tricky to figure out how to debug. Any ideas? We're on MaaS 2.14