=== lotuspsychje__ is now known as lotuspsychje
=== genii-core is now known as genii
=== cpaelzer_ is now known as cpaelzer
[19:51] <teward> *prods cpaelzer and drops a bug in their lap for review*  https://bugs.launchpad.net/bugs/1948699
[19:51] <ubottu> Launchpad bug 1948699 in nginx (Ubuntu) "Please enable luajit for arm64" [Undecided, Incomplete]
[19:52] <teward> 18.04 is what they're looking for, but I don't think that's SRUable
[19:52] <teward> and I'm going to "Won't Fix" for later releases.
[20:15] <jrwr> having some issues with deploying charms with JuJu and MAAS -- Using LXD I'm getting a "waiting for machine" for deploying any charm into LXD, Google has failed me on trying to fix this issue, and logs are not helpful, the container is started -- Here is some output from JuJu, Including the machine log https://pastebin.ubuntu.com/p/sKG6Synby6/
[20:20] <sarnold> jrwr: how about lxc list? lxc warning list? maybe there's something in the lxd logs that explains why those units aren't starting
[20:22] <jrwr> https://pastebin.ubuntu.com/p/t4RxWWQNV6/
[20:22] <jrwr> Doesn't look like it
[20:22] <jrwr> I did notice that if I get into the container it has no networking
[20:24] <jrwr> @sarnold its got route, ip is correct, can't ping anything, can't curl the MAAS server
[20:25] <sarnold> hm. I've got those same two warnings on my laptop; I don't know if it's entirely harmless or not but probably not related
[20:26] <jrwr> its def networking related
[20:26] <jrwr> brctl is empty
[20:28] <sarnold> does maas 'own' the lxd instances? is it supposed to manage the bridges, storage, etc, for the lxds? or are those supposed to be up and working before maas enrolls them?
[20:28] <jrwr> looks like juju is ment to handle that itself
[20:28] <jrwr> I guess if its not, then thats a failing of the openstack guides
[20:29] <jrwr> and it /never/ says you need to setup lxd, as the MAAS/JuJu deployed machine should have it pre-configured
[20:42] <jrwr> let me use this guide and see if it happens again https://jaas.ai/openstack-base
[20:42] <jrwr> as I was using the one Ubuntu homepage links to on openstack's website
[20:43] <jrwr> (and was broken in several places anyway)
[20:45] <sarnold> jrwr: there's probably a link near the bottom of the pages for filing bug reports -- please do use that if you find problems :)
[22:06] <jrwr> It would help if every charm I read links to a non-existing guide https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/xena/
[22:20] <sarnold> jrwr: https://github.com/canonical-web-and-design/jaas.ai/issues/665
[22:20] <ubottu> Issue 665 in canonical-web-and-design/jaas.ai "dead link" [Open]
[22:21] <jrwr> <3
[22:28] <trippeh> w
[22:28] <trippeh> err.
[22:29] <TJ-> heads up for any users of Nodejs and ua-parser-js that may not have see this - critical malware infection on the NPM repository for versions 0.7.29, 0.8.0, 1.0.0 and *any* machine that has installed/executed it should be considered completely compromised remotely. https://github.com/advisories/GHSA-pjwm-rvh2-c87w  - Ubuntu versions are too old to be affected.
=== sarnold_ is now known as ubuntuirccouncil