Juju might not be recognzing some OpenStack environment variables (see comments)

[Michael Skalka]

When bootstrapping a Juju controller against and existing OpenStack cloud if the 'domain-name' field is set in credentials.yaml the bootstrap fails with the following error:

ubuntu@OrangeBox68:~$ juju bootstrap test-stack --bootstrap-series xenial --config external-network=ext-net --config network=int-net --config use-floating-ip=true --metadata-source /home/ubuntu/simplestreams
Creating Juju controller "test-stack-RegionOne" on test-stack/RegionOne
Looking for packaged Juju agent version 2.5-rc1 for amd64
No packaged binary found, preparing local Juju agent binary
Launching controller instance(s) on test-stack/RegionOne...
ERROR failed to bootstrap model: cannot start bootstrap instance: cannot set up groups: failed to create a security group with name: juju-c0f8b1f0-0de4-4b3f-85fc-64abf0c5781a-4776d32b-0d68-446b-86f5-e77c17d0f616
caused by: request (http://172.27.69.80:9696/v2.0/security-groups) returned unexpected status: 400; error info: {"NeutronError": {"message": "Running without keystone AuthN requires that tenant_id is specified", "type": "HTTPBadRequest", "detail": ""}}

This was reproduced in both 2.5-rc1 and latest stable (2.4.7). Setting this field in credentials.yaml to "" results in a successful bootstrap.

[Richard Harding (rharding)]

This might also tie into https://bugs.launchpad.net/juju/+bug/1772649 though they're slightly different with one being around autoload-credentials.

[Fabrizio Cardarello (f.cardarello)]

After a few try those are the right option: juju version 2.6.2
credentials:
  cloud-openstack:
    default-region: RegionOne
    test:
      auth-type: userpass
      domain-name: ''
      password: password
      project-domain-name: admin_domain
      tenant-id: 8650020e13774c0aaa73e1e173ce8adf
      tenant-name: kubernetes
      user-domain-name: admin_domain
      username: admin
      version: "3"

[Tim McNamara (tim-clicks)]

This bug has been referenced by a discourse post, where another workaround has been found:

https://discourse.jujucharms.com/t/1628/3?u=timclicks

[Heather Lanigan (hmlanigan)]

Hit again, reported via discourse post:
https://discourse.jujucharms.com/t/juju-bootstrap-error-from-openstack/2158

[Anastasia (anastasia-macmood)]

Removing from a milestone as this work will not be done in 2.5 nor 2.6 series.

[Adam Dyess (addyess)]

Using the 2.8.6 snap installed client. We confirmed the OS_PROJECT_ID environment variable was set, so when bootstrapping, we didn't fill in the 'tenant_id' or 'tenant_name' options.

Because we didn't fill them in, the juju client picked the user's default project id from openstack rather than the one in the environment variables and tried to bootstrap the controller in the wrong project.

I think this bug is probably the closest relative because something isn't quite right with reading the OS_* environment variables.

[Pen Gale (pengale)]

I think that the Juju client might be lagging behind OpenStack in terms of which environment variables it pays attention to. We should audit the client and update it as necessary.

[Juan M. Tirado (tiradojm)]

Please reopen if the issue persists.