Versionless GET on keystone gives different answer with port 5000 and 35357

[David Kranz]

On a system with both v2/v3 (devstack), using 35357 shows only v3.

5000:
<versions xmlns="http://docs.openstack.org/identity/api/v2.0">
<version status="stable" updated="2013-03-06T00:00:00Z" id="v3.0">
<media-types>
<media-type base="application/json" type="application/vnd.openstack.identity-v3+json"/>
<media-type base="application/xml" type="application/vnd.openstack.identity-v3+xml"/>
</media-types>
<links>
<link href="http://devstack-neutron:5000/v3/" rel="self"/>
</links>
</version>
<version status="stable" updated="2014-04-17T00:00:00Z" id="v2.0">
<media-types>
<media-type base="application/json" type="application/vnd.openstack.identity-v2.0+json"/>
<media-type base="application/xml" type="application/vnd.openstack.identity-v2.0+xml"/>
</media-types>
<links>
<link href="http://devstack-neutron:5000/v2.0/" rel="self"/>
<link href="http://docs.openstack.org/" type="text/html" rel="describedby"/>
</links>
<link href="http://devstack-neutron:5000/v2.0/" rel="self"/>
<link href="http://docs.openstack.org/" type="text/html" rel="describedby"/>
</version>
</versions>

35357:
<versions xmlns="http://docs.openstack.org/identity/api/v2.0">
<version status="stable" updated="2013-03-06T00:00:00Z" id="v3.0">
<media-types>
<media-type base="application/json" type="application/vnd.openstack.identity-v3+json"/>
<media-type base="application/xml" type="application/vnd.openstack.identity-v3+xml"/>
</media-types>
<links>
<link href="http://devstack-neutron:35357/v3/" rel="self"/>
</links>
</version>
</versions>

[Adam Young (ayoung)]

keystone/service.py: _VERSIONS is a global, and updated first with v3, and then with v3.

[Lance Bragstad (lbragstad)]

Related blueprint that is approved in the keystone-specs repo:

https://github.com/openstack/keystone-specs/blob/master/specs/juno/json-home.rst

[Brant Knudson (blk-u)]

I tried this running keystone-all and both versions were given.

[Brant Knudson (blk-u)]

It happens when running keystone in wsgi.

[Brant Knudson (blk-u)]

oh, I was just looking at this code, so know what the prob is... only one of the public / private functions registers v2 with controller.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/118902
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=020f14deb30d3f6650e4d57a27ad56926f634b27
Submitter: Jenkins
Branch: master

commit 020f14deb30d3f6650e4d57a27ad56926f634b27
Author: Brant Knudson <email address hidden>
Date: Wed Sep 3 15:05:41 2014 -0500

    Add test for single app loaded version response

    There was no test that showed what the version response is when
    only a single application (public or admin) is loaded.

    The test shows that the response is incorrect for the admin
    application.

    Change-Id: I1fb1789c465d3f587077e3817a8eb2da54e28c63
    Partial-Bug: #1343579

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/118757
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=0ad8d079afa214dddfd9b9b30d64bc454801e95f
Submitter: Jenkins
Branch: master

commit 0ad8d079afa214dddfd9b9b30d64bc454801e95f
Author: Brant Knudson <email address hidden>
Date: Wed Sep 3 14:51:14 2014 -0500

    Fix admin server doesn't report v2 support in Apache httpd

    The Keystone server version response would only include v3 when
    Keystone was running in Apache httpd. It should have also included
    the v2.

    Change-Id: Ib471539beda746d085adae1e72ab0dc1e0fb41e0
    Closes-Bug: #1343579