Cannot use cinderclient with keystone v3 and OS_TENANT_NAME unset

[Ian Cordasco]

Cinderclient will error early if no environment variable is set for OS_TENANT_NAME. With it set, you can use Keystone v3 for authentication but the environment variable is meaningless for Keystone v3.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/199595
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=8afc06c562ac8c189fae6ded7cc50f1b579f06c4
Submitter: Jenkins
Branch: master

commit 8afc06c562ac8c189fae6ded7cc50f1b579f06c4
Author: Ian Cordasco <email address hidden>
Date: Wed Jul 8 09:37:07 2015 -0500

    Remove unnecessary check for tenant information

    Keystone v3 has changed the name of tenants to projects which means that
    OS_TENANT_NAME is meaningless in a cloud where v3 is the default
    authentication version. As such, if a user does not have OS_TENANT_NAME
    enabled, cinderclient will not work even though it has checks for v3
    immediately below this check (and the same check replicated further
    below that). Removing this allows cinderclient to work with Keystone v3
    without setting OS_TENANT_NAME unnecessarily.

    Further, the check for project information was incorrectly referring to
    project_domain_name and project_domain_id instead of
    os_project_domain_name and os_project_domain_id.

    Closes-bug: 1472636
    Change-Id: Ifabb4a2aec070c00349e794364a71394feea99f1

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/204147

[OpenStack Infra (hudson-openstack)]

Change abandoned by Ian Cordasco (<email address hidden>) on branch: stable/kilo
Review: https://review.openstack.org/204147
Reason: Kilo is only accepting security fixes at this point.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-cinderclient 1.4.0 release.