[04:35] <mup> Bug #1873729 opened: LXD pod host does not have snap OS info <blocking-ui> <MAAS:New> <https://launchpad.net/bugs/1873729>
[14:18] <mup> Bug #1873879 opened: Storage level testing (Hard Drives) is systematically failing. <MAAS:New> <https://launchpad.net/bugs/1873879>
[15:59] <colombrican> Hello, need some advice ... just did a base upgrade of a maas 2.3/16.04 server to 18.04, but when I run an apt upgrade i keep getting an error pointing to LXD bridge and accessing the MAAS url gives me a 404 not found error
[16:00] <colombrican> Old bridge configuration detected in /etc/default/lxd-bridge, upgradingUnsetting deprecated profile optionsAttempting to kill current lxd-bridgeBringing down and renaming existing bridge lxdbr0 to lxd-upgradeCreating a new LXD bridgeMoving the old bridge into placeConfiguring the new LXD bridgeSetting IPv4 network to 10.80.0.15/24Error: Failed to
[16:00] <colombrican> run: dnsmasq --strict-order --bind-interfaces --pid-file=/var/lib/lxd/networks/lxdbr0/dnsmasq.pid --except-interface=lo --interface=lxdbr0 --quiet-dhcp --quiet-dhcp6 --quiet-ra --listen-address=10.80.0.15 --dhcp-no-override --dhcp-authoritative --dhcp-leasefile=/var/lib/lxd/networks/lxdbr0/dnsmasq.leases
[16:00] <colombrican> --dhcp-hostsfile=/var/lib/lxd/networks/lxdbr0/dnsmasq.hosts --dhcp-range 10.80.0.2,10.80.0.254,1h -s lxd -S /lxd/ --conf-file=/var/lib/lxd/networks/lxdbr0/dnsmasq.raw -u lxd: dnsmasq: failed to create listening socket for 10.80.0.15: Address already in usedpkg: error processing package lxd (--configure): installed lxd package post-installation
[16:00] <colombrican> script subprocess returned error exit status 1Processing triggers for libc-bin (2.27-3ubuntu1) ...Errors were encountered while processing: lxdE: Sub-process /usr/bin/dpkg returned an error code (1)
[16:42] <eXtace> the docs for curtin customiation are a big ambiguous 'The machine needs to be the machine name, as shown in the web UI URL."  The web UI for the machine doesn't have it's name,  just it's identifier,  I've tried every possible combination but cannot get it to work,  can anyone else wexplain how they did this to get a MACHINE SPECIFIC
[16:42] <eXtace> curtin_userdata script in place?
[16:42] <eXtace> curtin_userdata_custom_amd64_generic_xenial_<shortname> curtin_userdata_custom_amd64_generic_xenial_<fqdn> curtin_userdata_custom_amd64_generic_xenial_<id_from url>   none of these work
[16:43] <eXtace> curtin_userdata_custom does (we are using custom images),  but I need a one-off to test against a single machine so I don't affect any other nodes being provisioned.
[16:54] <eXtace> ok,  figured it out,  you cannot use "xenial" like in the examples above you need to use the name of the boot resource you created, and the _custom_ IS REQUIRED.
[16:55] <eXtace> curtin_userdata_custom_amd64_generic_<IMAGE_NAME>_<SHORTNAME>  where IMAGE_NAME is pulled from maas <profile> boot-resources read  and SHORTNAME should be obvious...  The docs need improvement....
[18:36] <mup> Bug #1873879 changed: Storage level testing (Hard Drives) is systematically failing. <MAAS:New> <https://launchpad.net/bugs/1873879>
[18:39] <mup> Bug #1873879 opened: Storage level testing (Hard Drives) is systematically failing. <MAAS:New> <https://launchpad.net/bugs/1873879>
[18:51] <mup> Bug #1873879 changed: Storage level testing (Hard Drives) is systematically failing. <MAAS:New> <https://launchpad.net/bugs/1873879>
[21:52] <mup> Bug #1873962 opened: Machines can have inconsistent testing status <MAAS:New> <https://launchpad.net/bugs/1873962>
[21:55] <mup> Bug #1873962 changed: Machines can have inconsistent testing status <MAAS:New> <https://launchpad.net/bugs/1873962>
[22:13] <mup> Bug #1873962 opened: Machines can have inconsistent testing status <MAAS:New> <https://launchpad.net/bugs/1873962>