[03:54] <bmorriso> getting an error util.py[WARNING]: Failed fetching metada from url http://<maas url>/MAAS/metadata/curtin -- any idea what causes this? Sometimes the <maas url> is actually 169.254 (like it isn't getting an IP via DHCP or something). This used to work but hasn't since 1.8
[04:26] <bmorriso> Nothing in /var/log/maas/* to indicate why it is failing
[04:51] <bmorriso> It finally fails with a message on the terminal: cc_final_message.py[WARNING]: Used failback datasource
[04:53] <bmorriso> Reading the docs here https://maas.ubuntu.com/docs/troubleshooting.html#maas-datasource about datasource /etc/cloud/cloud.cfg.d/*_cmdline_url.cfg doesn't exist on my MAAS server
[06:39] <bmorriso> Where are the images stored on the host? I'd like to delete them and start over.
[09:28] <mup> Bug #1485932 opened: EventualResult.cancel() is not called on timed-out calls <tech-debt> <MAAS:Triaged> <https://launchpad.net/bugs/1485932>
[11:55] <mup> Bug #1486003 opened: Error in migration: maasserver:0161_create_missing_physical_interfaces <MAAS:New for blake-rouse> <https://launchpad.net/bugs/1486003>
[14:35] <mup> Bug #1485139 opened: MAAS should let you specify which interfaces you want to bind tftp on. <MAAS:Triaged> <maas (Ubuntu):New> <https://launchpad.net/bugs/1485139>
[14:50] <mup> Bug #1485139 changed: MAAS should let you specify which interfaces you want to bind tftp on. <MAAS:Triaged> <https://launchpad.net/bugs/1485139>
[15:02] <mup> Bug #1485139 opened: MAAS should let you specify which interfaces you want to bind tftp on. <MAAS:Triaged> <maas (Ubuntu):New> <https://launchpad.net/bugs/1485139>
[15:05] <mup> Bug #1485139 changed: MAAS should let you specify which interfaces you want to bind tftp on. <MAAS:Triaged> <https://launchpad.net/bugs/1485139>
[15:37] <bmorriso> getting an error util.py[WARNING]: Failed fetching metada from url http://<maas url>/MAAS/metadata/curtin -- any idea what causes this? Sometimes the <maas url> is actually 169.254 (like it isn't getting an IP via DHCP or something). This used to work but hasn't since 1.8
[17:02] <mup> Bug #1289158 changed: The version of the package is not displayed on the MAAS UI <doc> <ui> <MAAS:Fix Released by blake-rouse> <https://launchpad.net/bugs/1289158>
[17:02] <mup> Bug #1438652 changed: Wrong spacing in the display of the "machine output" <ui> <MAAS:Fix Released by blake-rouse> <https://launchpad.net/bugs/1438652>
[17:02] <mup> Bug #1441864 changed: 1.8b1: Can't filter servers by owner correctly if owner is subset of another owner <oil> <ui> <ux> <MAAS:Fix Released by blake-rouse> <MAAS 1.8:Fix Released by blake-rouse> <https://launchpad.net/bugs/1441864>
[23:22] <plars> I'm hitting a weird error on maas, it says "Boot image import process not started. Nodes will not be able to provision without boot images. Visit the boot images page to start the import."
[23:23] <plars> when I click the link to go to the page to start the import, I see no place to do it
[23:23] <plars> but I see the same message again, redirecting me to the page it's already on
[23:23] <plars> I have 14.04LTS and amd64 selected, and I've managed to deploy nodes from this environment just fine
[23:24] <plars> but I am getting weird errors when juju tries to download the image for lxc deployments, unsure if it's related to this
[23:24] <plars> any ideas where to look?