[00:17] <mup> Bug #1733442 opened: Cannot delete Virsh Pod <MAAS:In Progress by newell-jensen> <https://launchpad.net/bugs/1733442>
[14:10] <mup> Bug #1733600 opened: Custom images removed from Web UI still show up as an option during deploy in Web UI <MAAS:New> <https://launchpad.net/bugs/1733600>
[15:10] <mup> Bug #1733615 opened: [SRU] MAAS 2.3.0 <maas (Ubuntu):New> <maas (Ubuntu Xenial):New> <maas (Ubuntu Zesty):New> <maas (Ubuntu Artful):New> <https://launchpad.net/bugs/1733615>
[15:59] <heyya> So, I made some DNS changes to the MAAS files, and I noticed that the reverted.
[17:13] <mup> Bug # changed: 1550083, 1706723, 1730976, 1730985, 1731059, 1731298, 1731353, 1731887, 1732220, 1732444, 1732522, 1732536, 1732539, 1732561, 1732730, 1732768, 1732948, 1733015
[17:25] <roaksoax> heyya: MAAS manages DNS and they will be regenrated, what changes were you making ?
[17:57] <bviktor_> is it not possible to install the maas server on centos?
[18:13] <mup> Bug #1733442 changed: Cannot delete Virsh Pod <MAAS:Won't Fix by newell-jensen> <https://launchpad.net/bugs/1733442>
[18:44] <roaksoax> bviktor_: if you use the snap, it could be
[18:45] <roaksoax> we've not tested
[19:02] <heyya> roaksoax: I wanted to know how to make it recursive
[19:02] <heyya> as I am getting the following error. WARNING: recursion requested but not available
[19:03] <roaksoax> ?
[19:03] <heyya> DNS
[19:04] <heyya> dnssec-validation auto;
[19:05] <heyya> recursion;
[19:06] <heyya> this file : /etc/bind/maas/named.conf.options.inside.maas
[19:08] <heyya> when I dig against it, it does not resolve hostname from IP etc.
[19:21] <bviktor_> well if snaps are as "universal" as they claim it, it shouldn't need to be "tested" though...
[19:24] <bviktor_> oh, centos isn't even supported by snap anyway, oh well
[19:29] <roaksoax> https://docs.snapcraft.io/core/install
[19:30] <roaksoax> heyya: have you looked at the settings page in MAAS for the available configurable DNS settings ?
[19:31] <heyya> are you reffering to DHCP snippets?
[19:34] <heyya> sorry.. forgive the confusion.. ok.. all workig now
[19:34] <heyya> lol
[19:47] <heyya> I created a subnet and reserved dynamic range as I only need dhcp on a portion of that network.  There is an option to Enable "Managed allocation".  When I enable it, will it only enable dhcp on the "Reserve dynamic range" ?
[19:47] <heyya> as that's what I'm trying to achieve
[19:47] <heyya> I want to enable dhcp on a small portion of the network.
[20:01] <mup> Bug #1733686 opened: [2.x, pod] MAAS pods should be allowed to be placed in a zone, and all machines inside the pod should have the same zone <MAAS:New> <https://launchpad.net/bugs/1733686>
[20:22] <roaksoax> heyya: when you enable dhcp you only enable it on the 'dynamic' range
[20:22] <roaksoax> heyya: so you have to define a dynamic range to enable dhcp
[20:31] <mup> Bug #1733686 changed: [2.x, pod] MAAS pods should be allowed to be placed in a zone, and all machines inside the pod should have the same zone <MAAS:New> <https://launchpad.net/bugs/1733686>
[21:39] <heyya> roaksoax: yeah, i figured i out.
[22:46] <xygnal> TJ-: ipxe iso aways fails on ldlinux.c32
[22:46] <xygnal> but my own sniffs from MAAS showed it for farther than two files, and ldlinux.c32 is not the first file