reproducer-quickstart.sh doesn't work with keystone v3

Bug #1750585 reported by Sofer Athlan-Guyot
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
New
Medium
Unassigned

Bug Description

Hi,

using a plain devstack deployment on one host as the cloud provider, the reproducer script doesn't work.

It forces the usage of keystone v2, (OS_TENANT_NAME required). Even removing that in the reproducer script isn't enough as the os_tenant_name is checked as well inside the play.

The problem is that using that devstack deployment, even when adding ENABLE_IDENTITY_V2=True in local.conf, we get an error:

fatal: [localhost]: FAILED! => {"changed": true, "cmd": "openstack image list --long -f value -c ID --property latest=centos-7-latest", "delta": "0:00:00.732647", "end": "2018-02-20 15:53:34.532231", "msg": "non-zero return code", "rc": 1, "start": "2018-02-20 15:53:33.799584", "stderr": "(http://172.30.0.10/identity/v2.0/tokens): The resource could not be found. (HTTP 404) (Request-ID: req-23232051-26eb-41f8-b7c6-c1a04fcb45aa)", "stderr_lines": ["(http://172.30.0.10/identity/v2.0/tokens): The resource could not be found. (HTTP 404) (Request-ID: req-23232051-26eb-41f8-b7c6-c1a04fcb45aa)"], "stdout": "", "stdout_lines": []}

to reproduce, install devstack, stable/queens branch (optional add the ENABLE_IDENTITY_V2=True in local.conf) get the v2 configuration of demo or alt_demo (admin has just v3 credentials) and run the script.

So v3 should be supported to ease that scenario.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.