Network Spaces Issues with LXD on Juju 2.2

[Peter Sabaini]

You might be hitting https://bugs.launchpad.net/juju/+bug/1698443

cheers,
peter.

On 22.06.17 16:15, Subhranshu Dwivedi wrote:
> Hi Team,
> 
> I am trying to install openstack using bundle.yaml, on MaaS 2,0, with
> network spaces using Juju .2.2,
> 
> Now the problem is that Lxd containers are not booting with defined
> network spaces, I am defining it as following in the bundle.yaml:
> 
>   ceph-mon:
>     charm: cs:xenial/ceph-mon
>     num_units: 3
>     bindings:
>       "": maas
>       client: internal-api
>       cluster: internal-api
>       mon: internal-api
>       osd: internal-api
>     to:
>       - 'lxd:1'
>       - 'lxd:2'
>       - 'lxd:3'
> 
> Where available spaces for me are as following:
> Space              Subnets
> internal-api       xxx.xxx.xxx.xxx/24
> maas               xxx.xxx.xxx.xxx/24
> 
> The lxd instance just boots with internal-api and drops the default
> bindings,
> 
> And as a matter of fact the same bundle worked on Juju 2.1 and MaaS 2.0
> 
> Please suggest,
> 
> Best Regards
> Subhranshu
> 
> 
> 
> 
> 
> 
> 
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/juju/attachments/20170622/cd5298ae/attachment.pgp>