[01:06] <mup> Bug #1451490 changed: Installation failed with exception: Unexpected error while running command. <curtin:Triaged> <MAAS:Invalid> <https://launchpad.net/bugs/1451490>
[08:10] <jgrassler> Good morning.
[08:11] <jgrassler> Is there some kind of trick to getting a hwe-u Kernel into a MAAS controller's boot images?
[08:12] <jgrassler> http://maas.ubuntu.com/docs1.5/hardware-enablement-kernels.html seems to suggest it being a simple matter of adding 'hwe-u' to the 'subarches' key for the release in question, but reality looks otherwise:
[08:12] <jgrassler> It works fine for a hwe-t Kernel, but for the hwe-u nothing gets added.
[13:27] <etbusch> Good morning all, I'm doing my first install, and am having trouble gettign my second NIC to act as a dhcp server, after putting in settings, ifconfig states that the interface is still down. Nodes connected to the second nic don't see a DHCP server when they boot PXE. What am I doing wrong here?
[14:29] <mup> Bug #1451852 was opened: Legacy VMware "add chassis" option should be removed <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1451852>
[14:29] <mup> Bug #1451856 was opened: maas-proxy squid file limit reached <MAAS:New> <https://launchpad.net/bugs/1451856>
[14:29] <mup> Bug #1451857 was opened: Probe-and-enlist for VMware needs to update VM config to use PXE boot <MAAS:Triaged by mpontillo> <https://launchpad.net/bugs/1451857>
[15:17] <mup> Bug #1451591 changed: MAC Address UI fields appear to disallow the selection of field content <MAAS:Invalid> <https://launchpad.net/bugs/1451591>
[16:17] <mup> Bug #1427160 changed: d-i allocates all disk space to /home <cts> <openstack> <MAAS:Invalid> <partman-auto (Ubuntu):Triaged> <https://launchpad.net/bugs/1427160>
[22:32] <mup> Bug #1452053 was opened: Edit node name on node details page switches between '*.maas' and '*.local' <ui> <MAAS:New> <https://launchpad.net/bugs/1452053>