mitaka trust notifier won't work

[Mehdi Abaakouk]

Hi,

When the default auth-type is used in mitaka, the trust notifier don't work

downstream reported issue: https://bugzilla.redhat.com/show_bug.cgi?id=1364052

Cheers,

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/365640
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=ba9d8687a23a7aa00abcdce74021c92e82292e51
Submitter: Jenkins
Branch: stable/mitaka

commit ba9d8687a23a7aa00abcdce74021c92e82292e51
Author: Mehdi Abaakouk <email address hidden>
Date: Mon Sep 5 15:13:57 2016 +0200

    Restore trust workaround for legacy auth

    Before mitaka, we were not supporting keystone v3 and we were
    expecting to have the auth_url ending with /v2.0 to ensure
    v2 keystone API. We were using a workaround to force v3 for trust
    keystone client, and when we moved to keystoneauth1 we removed this workaround
    but it's still needed.

    This change restores it. It ensures the endpoint is a v3 endpoint when
    the user enter a v2 endpoint and set domain to 'default' that was the
    only that worked before, because we were not really support keystone v3.

    This is not a backport because it fixes a bug in deprecated (and already removed from master) code.

    Closes-bug: #1620499
    Change-Id: Idf474348ab4d49073dc5561caf90e151c4138819

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/aodh 2.0.5 release.