Juju fails to bootstrap on OpenStack with 'domain-name' set in credentials.yaml

Bug #1806985 reported by Michael Skalka on 2018-12-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

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 ( 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.

Michael Skalka (mskalka) on 2018-12-05
description: updated
tags: added: cpe-onsite
Changed in juju:
status: New → Triaged
Richard Harding (rharding) wrote :

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

Changed in juju:
importance: Undecided → High
milestone: none → 2.5.0
milestone: 2.5.0 → 2.5.1
Ian Booth (wallyworld) on 2019-01-28
Changed in juju:
milestone: 2.5.1 → 2.5.2
Changed in juju:
milestone: 2.5.2 → 2.5.3
Changed in juju:
milestone: 2.5.3 → 2.5.4
Changed in juju:
milestone: 2.5.4 → 2.5.5
Changed in juju:
milestone: 2.5.6 → 2.5.8

After a few try those are the right option: juju version 2.6.2
    default-region: RegionOne
      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"

Changed in juju:
milestone: 2.5.8 → none
milestone: none → 2.7-beta1
Tim McNamara (tim-clicks) wrote :

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


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers