PCdude | hello everybody :) | 17:03 |
---|---|---|
PCdude | hey admcleod_ lazyPower magicaltrout | 17:06 |
pragsmike | greets | 17:23 |
pragsmike | In beta17, using MAAS cloud, I'm having trouble, maybe related to [[https://bugs.launchpad.net/juju/+bug/1607964][#1607964]] but puzzlingly different. | 17:23 |
mup | Bug #1607964: juju2, maas2, lxd containers started with wrong IP, rely on dhclient to switch things <landscape> <juju:Triaged by rharding> <https://launchpad.net/bugs/1607964> | 17:23 |
pragsmike | What I'm seeing looks more like [[https://bugs.launchpad.net/juju/+bug/1566801][#1566801]] is still happening, but that's marked as fixed in beta15. | 17:24 |
mup | Bug #1566801: LXD containers /etc/network/interfaces as generated by Juju gets overwritten by LXD container start <2.0> <cdo-qa-blocker> <landscape> <network> <juju:Fix Released by frobware> <https://launchpad.net/bugs/1566801> | 17:24 |
pragsmike | 'juju add-machine lxd:1' creates a container, but it doesn't have an address allocated by MAAS. | 17:24 |
pragsmike | Isn't it supposed to? | 17:24 |
pragsmike | It gets an address via dhcp from LXD's dnsmasq, which I didn't think was supposed to happen. | 17:25 |
pragsmike | I do have agent-stream: devel in the controller bootstrap, and confirmed that the host machine's agent.conf says 'upgradedToVersion: 2.0-beta17' | 17:28 |
=== zeus is now known as Guest64781 | ||
pragsmike | can someone explain what the intended behavior is (ie what address should the container get) so I can help troubleshoot this? | 17:40 |
PCdude | http://askubuntu.com/questions/820925/how-do-i-set-a-dns-server-in-maas-that-will-be-passed-on-to-the-nodes | 20:26 |
pragsmike | I worked around it by bridging the containers to the host's interface, which allowed them to get DHCP'ed (dynamically) by MAAS | 20:48 |
pragsmike | but that's a crock, and I'd like to know how to do it right | 20:48 |
=== mwhudson_ is now known as mwhudson |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!