[01:05] <mup> Bug #1666343 opened: would be nice if controller page linked to logs <maas-at-home> <MAAS:New> <https://launchpad.net/bugs/1666343>
[03:42] <mup> Bug #1627016 changed: [2.1, rev5385] MAAS reports there are missing rack connections but no error logs <uosci> <MAAS:Triaged> <https://launchpad.net/bugs/1627016>
[06:33] <chaithu> Hi All,
[06:38] <chaithu> need some help regading DHCP when PXE booting a Hardware using MAAS
[06:40] <chaithu> Problem: HW fails to to get the DHCP IP address when booting up the Linux image . Initial Bootp/DHCP request goes though fine.
[06:42] <chaithu> after digging with packet capture on MAAS server. we found that there are multiple DHCP servers and they are sending  DHCP NAK being sent by the not serving DHCP servers.
[06:43] <chaithu> So PXEclient was able to process the correct ACK request ignoring other  NAK requests
[06:44] <chaithu> But the Linux ipconfig client using by the linux image was not able to do the process the correct DHCP ACK request (There are multiple DHCP NAK packets from not serving servers)
[08:14] <kklimonda> how do I disable (and keep disabled) dnssec in MAAS?
[08:16] <kklimonda> ah, it's in settings
[09:10] <mup> Bug #1666448 opened: [Device Discovery] The "Discovery Enabled" label is a bit confusing <MAAS:New> <https://launchpad.net/bugs/1666448>
[09:25] <mup> Bug #1666448 opened: [Device Discovery] The "Discovery Enabled" label is a bit confusing <MAAS:New> <https://launchpad.net/bugs/1666448>
[11:46] <mup> Bug #1666478 opened: Feature Request Allow grub to multi-boot MAAS images <MAAS:New> <https://launchpad.net/bugs/1666478>
[13:47] <mup> Bug #1666521 opened: MAAS does not detect RAM in newly commissioned VMWARE VM's <MAAS:New> <https://launchpad.net/bugs/1666521>
[14:39] <eeemil> What is the difference between fabric and space?
[15:54] <roaksoax> eeemil: fabric is a or a set of switches (contains vlans)
[15:54] <roaksoax> eeemil: a space is a set of subnets that can communicate with each other via L2
[16:57] <ybaumy> my ens192 interface isnt getting configured by cloud-init when commissioning. therefor i have no internet connection and the commissioning fails. the ens192 interface is getting the ip from a different dhcp server. is this a problem?
[17:25] <ybaumy> or is it something else then cloud-init. im kinda lost. i dont know where to start. how are network interfaces configured?
[17:58] <ybaumy> i figured that i have to setup on the nodes screen each individual node for itself which network the interface should be set
[17:58] <ybaumy> lets see how the commissioning goes
[18:37] <vogelc> What is the maas cli command to "acquire" or "allocate" a machine to a user?
[18:56] <roaksoax> vogelc: maas <user> machines allocate
[21:21] <mup> Bug #1665839 opened: Compose sometimes composes machines with the same node_id <MAAS:In Progress by newell-jensen> <MAAS RSD :In Progress by newell-jensen> <https://launchpad.net/bugs/1665839>
[22:15] <mup> Bug #1666698 opened: rackd not generating a dhcpd.conf in a timely manner  <MAAS:New> <https://launchpad.net/bugs/1666698>
[22:15] <mup> Bug #1666700 opened: maas allocating new IP to existing MAC/IP pair when old IP is free <MAAS:New> <https://launchpad.net/bugs/1666700>
[22:19] <stormmore> hmmm am I missing something or is there no documentation on enabling https for the UI / API?
[22:20] <pmatulis> stormmore, there was a thread on that recently on the maas-devel m/l
[22:22] <stormmore> pmatulis, thanks will go digging
[23:30] <mup> Bug #1666719 opened: [2.1.3] A node enlistment fails to contact metadata service <MAAS:New> <https://launchpad.net/bugs/1666719>