devmode does not create a properly formated clouds.yaml

[Alex Schultz]

If you have a v3 stackrc file that does not include OS_TENANT_NAME (which is not defined in a v3 file), it does not properly generate the cloud.yaml with a project_name set.

example stackrc:

export OS_USERNAME=myproject
export OS_PROJECT_NAME=myproject
export OS_AUTH_URL=https://foocloud/
export OS_PASSWORD=somepassword
export OS_IDENTITY_API_VERSION=3
export OS_REGION_NAME=regionOne
unset OS_TENANT_NAME

Running 'bash devmode.sh --no-gate --ovb' fails during stack deployment because the ~/.quickstart/cloud.yaml looks like:

clouds:
  rdocloud:
    auth:
      username: myproject
      password: somepassword
      project_name:
      auth_url: https://foocloud/
    region_name: regionOne

Workaround:
export OS_TENANT_NAME=$OS_PROJECT_NAME prior to running devmode.sh

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/512055

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/512055
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=e924839f67282ef303750ad7241bde781283e59c
Submitter: Zuul
Branch: master

commit e924839f67282ef303750ad7241bde781283e59c
Author: Alex Schultz <email address hidden>
Date: Sat Oct 14 16:37:50 2017 -0600

    Fix clouds.yaml generation

    Previously the os_tenant_name was being used to generate the
    project_name in clouds.yaml. But if your credentials environment did not
    include an OS_TENANT_NAME declaration but did include an OS_PROJECT_NAME,
    this could result in a bad clouds.yaml and auth failures. This change
    adds the tenant_name in the clouds.yaml as well as setting project_name
    to use os_project_name while still falling back to the previous
    os_tenant_name. Additionally since this is a v2.0/v3 issue, let's
    support properly defining the identity api version if defined.

    Change-Id: Iea728eabc1bc00facb3f208a69dbafaa630912b2
    Closes-Bug: #1723669

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-quickstart 2.1.1 release.