[04:18] Bug #1748010 changed: "Unconfigured" interface in MAAS becomes DHCP interface on deployed node === frankban|afk is now known as frankban [09:06] Bug #1762673 opened: maas insists on running the proxy, even when it's disabled [09:15] Bug #1762673 changed: maas insists on running the proxy, even when it's disabled [09:18] Bug #1762673 opened: maas insists on running the proxy, even when it's disabled [13:37] Bug #1762579 changed: HA region controllers offer different NTP servers [13:37] Bug #1762673 changed: maas insists on running the proxy, even when it's disabled [13:46] Bug #1762673 opened: maas insists on running the proxy, even when it's disabled === frankban is now known as frankban|afk [20:24] Hey guys, silly question, but in a MAAS subnet, if I set up a reserved range, say 172.0.0.1 to 172.0.0.100, MAAS WILL NOT issue any IP addresses from that range, correct? [20:27] also, if that range includes static assigned IPs for BMCs does that mean MAAS can no longer access those BMCs? [20:27] roaksoax, ^^ [20:28] just trying to figure out why I suddenly can not access either BMC (directly) nor can MAAS. It coudl be a lab issue though. [21:20] Bug #1762836 opened: 2.4 DHCP service not started till system restarted [21:23] Bug #1762836 changed: 2.4 DHCP service not started till system restarted [22:49] I cna't seem to comission a node. [22:50] Node says power On