=== mpjetta_ is now known as mpjetta [06:54] crodriguez: if it hung there please make sure your client can reach the VM that came up and ssh to that VM and check the cloud-init logs on how it got along. === nammn_de_ is now known as nammn_de [14:13] wallyworld: https://github.com/juju/juju/pull/10643 [14:55] crodriguez, did you fix the bootstrap issue? [14:56] no. It's probably an issue in the dns of my vms vs the host, but even once I make sure my dns works on the vm, the script stays hanging. I'm trying to find the reaktime logs from that step.. [14:59] pmatulis: I see that this function in juju's code has a ProgressWirter pointed to ctx.GetStderr(), but I can't find where this may be stored [15:01] nvm I think it just means that it'll print out only errors [15:05] crodriguez, maybe if you describe your env. where is juju client and what cloud type? [15:12] pmatulis: I'm trying to bootstrap an openstack controller from a cloud I deployed with the fce tool. I can access my vms, they have dns and internet access. Just being able to find the bootstrap detailed logs would help a lot. the --debug command doesn't explicit what is blocking [15:21] crodriguez, you can try passing --keep-broken and then inspect the instance [15:22] (if you can) [15:22] default behaviour of juju is to destroy the instance if it cannot be reached [15:26] When I'm creating a new juju controller, can I get it to use a different LXD (notwork) profile? [15:26] *network [15:26] Changing the controller profile after doesn't seem to work [15:27] Maybe I'll just have to edit the default LXD profile to meet my requiements? [15:30] danboid: Changing the default profile is the way to do it currently. [15:30] manadart, OK thanks [15:35] When running juju bootstrap, what does [15:35] ERROR no addresses match [15:35] mean? [15:45] I've found a couple of bug reports indicating juju bootstrap doesn't work well if you are not using lxdbr0 [15:45] I need to use a macvlan profile [15:47] The other option is creating the controller using lxdbr0 but then what do I need to modify within the controller container to chabe the addresses? [15:48] I would change it to use my macvlan profile after creating it [15:48] I've already tried doing this but it didn't update the controller address [15:53] I suppose the other option would be to not use LXD at all right? [15:53] How do I juju bootstrap to 'bare metal'? [15:54] Is that an option? [15:58] Apparently macvlan doesn't work with juju https://discourse.jujucharms.com/t/manual-network-setup-for-lxd-clustering/261 [15:59] I've never been able to access containers using an lxdbr0 bridge from outside of the LXD host, which ids what I need to do [16:00] and its why I was trying macvlan as that does enable external hosts to communicate [16:00] Am I missing something with lxdbr0? [16:09] manadart, I think you've answered my question here https://discourse.jujucharms.com/t/manual-network-setup-for-lxd-clustering/261 [16:12] That brigge config is anything but obvious so it seems like that should be covered / linked to in the juju docs. before / o the same page as controller bootstrapping, presuming it works [16:12] * before / on [16:14] The default lxdbr0 is only going to be useful to those who have all their juju containers running on the one host, it seems [16:47] wallyworld: +1 plz https://github.com/juju/charm-tools/pull/547. thanks! [16:47] I've tried following that guide but when lxd init asks if I'd like to use an existing bridge or interface it doesn't accept br0 nor the interface name [16:48] Oops! [16:49] I was trying to input br0 when the answe was yes :) [16:49] Time to go home I think :)