Hi, Running the bootstrap in --debug gives me this:
JUJU_DEV_FEATURE_FLAGS=address-allocation juju bootstrap --show-log --debug --constraints tags=4core 2015-11-09 21:47:29 DEBUG juju.environs.bootstrap bootstrap.go:112 using MTU 9000 for all created LXC containers' network interfaces 2015-11-09 21:47:30 INFO juju.cmd cmd.go:129 Starting new instance for initial state server 2015-11-09 21:47:30 DEBUG juju.provider.maas environ.go:145 address allocation feature enabled; using static IPs for containers: "juju-br0" then then the actual server doesn't end up with the bridge created. If I do not use the address allocation feature I end up with juju-br0 as expected. the surprising thing is that it definitely work with that feature as well. kind regards Pshem On Mon, 9 Nov 2015 at 20:13 Dimiter Naydenov <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 9.11.2015 04:23, Pshem Kowalczyk wrote: > Hi Pshem, > > Any chance you've used JUJU_DEV_FEATURE_FLAGS=address-allocation > during bootstrap? > > Can you have a look at /var/log/juju/machine-0.log? In the beginning > there should be lines like: > > "address allocation feature disabled; using juju-br0 bridge for all > containers" > > or alternatively: > > "address allocation feature enabled; using static IPs for containers: > juju-br0" > > Cheers, > Dimiter > > > Hi, > > > > I'm using MAAS and juju using lxc containers to spin up openstack > > components. I regularly destroy my enviornments to try some new > > settings. (juju 1.25, MAAS 1.8.2) > > > > Initially my setups would create a juju-br0 that contained eth0 and > > then bridged all LXCs to it (this way I could use MAAS DHCP to give > > IP addresses to containers). Somehow, between one test and the > > other juju is not creating juju-br0 any more, and my LXC containers > > end up living in lxcbr0 space with own DHCP server that gives them > > 10.0.3.0/24 <http://10.0.3.0/24> IPs (which breaks connectivity > > with anything outside of the machine) > > > > Clearly I must have changed something in my config, but my whole > > definition of MAAS environment is quite simple: > > > > maas: type: maas maas-server: 'http://10.201.7.219/MAAS/' > > maas-oauth: 'key here' bootstrap-timeout: 1800 lxc-default-mtu: > > 9000 lxc-clone: true allow-lxc-loop-mounts: true > > > > and I don't recall modifying it. > > > > How can I get back to juju-br0 (that joins eth0 and assumes its IP > > address)? > > > > kind regards Pshem > > > > > > > > > - -- > Dimiter Naydenov <[email protected]> > Juju Core Sapphire team <http://juju.ubuntu.com> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iQEcBAEBAgAGBQJWQEdiAAoJENzxV2TbLzHwdrcH/0WAQ0DVqK9PWVkHnpWsIUVQ > kKGfpESiEpj/uR2OpZ5ijzKdIRBY/DRZyuvLEv2EUta4cx6irb8P9k0M66X3+7ub > N3sXwK1m/b0I9H1u50dq269xwhUIS4Lu+pVdlIExZIbX8/9P0KxgARi3UXiBeAC7 > 5mawWFN7Pamxrnd0qZp6CGqExnC77q0vLLOqWXOewXkdBuIht6gEdq1+94e1ktVv > 64rr7LI5sEY1j+v/HgeuZi8CPi44fNUTD3MEVtc6Ow2XSNU63b9xmrp40jE2iU55 > islAdQU+VuUsyrcdp9hD1+6IiPcq/R82SIANumnPaNE7ONnRhHFOhhSxobZhYHo= > =T2Fq > -----END PGP SIGNATURE----- > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
