Bootstrapping on Openstack has external network name constraints

[Gary Mackenzie]

When bootstrapping Juju on an Openstack cloud, the errors shown in https://pastebin.canonical.com/209056/ are experienced depending on name of the external network.

If the external network name is 'Floating IPs' then provisioning fails as above logs.

If the external network name is 'external' (no other changes) then it succeeds.

Time-sensitive deployment so we've not been able to verify if the presence of spaces or capitals specifically breaks it. However the first is a fully valid network name in Openstack so should be supported.

[Heather Lanigan (hmlanigan)]

Gary,
Which version of juju are you using?
Are any compute and/or network availability zones configured in the OS deployment?
Can you try specifying the external network by UUID instead of name?

[Gary Mackenzie (5ello)]

ubuntu@k8s-client:~$ juju version
2.3.1-xenial-amd64

No network availability zones configured, single AZ for compute, out of the box Canonical Openstack deployment.

--model-default network=<ext net UUID> did not change the results.

[Heather Lanigan (hmlanigan)]

I'd suggest bootstrap --config external-network=<ext net UUID> --config
network=<private net UUID>, and if you have more than the default model,
also use --model-default

On Fri, Feb 2, 2018 at 10:28 AM, Gary Mackenzie <
<email address hidden>> wrote:

> ubuntu@k8s-client:~$ juju version
> 2.3.1-xenial-amd64
>
> No network availability zones configured, single AZ for compute, out of
> the box Canonical Openstack deployment.
>
> --model-default network=<ext net UUID> did not change the results.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1746984
>
> Title:
> Bootstrapping on Openstack has external network name constraints
>
> Status in juju:
> Triaged
>
> Bug description:
> When bootstrapping Juju on an Openstack cloud, the errors shown in
> https://pastebin.canonical.com/209056/ are experienced depending on
> name of the external network.
>
> If the external network name is 'Floating IPs' then provisioning fails
> as above logs.
>
> If the external network name is 'external' (no other changes) then it
> succeeds.
>
> Time-sensitive deployment so we've not been able to verify if the
> presence of spaces or capitals specifically breaks it. However the
> first is a fully valid network name in Openstack so should be
> supported.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1746984/+subscriptions
>

[Heather Lanigan (hmlanigan)]

To my knowledge the config is now up and running.

I was unable to attempt a reproduction of the space in the network name exactly, but I did attempt a reproduction with a space in the name of the network and didn't encounter the same problem. The resolution of a network name for OS juju is the same whether an internal or external network is specified.

Marking as incomplete until/unless more detail becomes available.

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]