noauth mode doesn't work

[John Schwarz]

Trying to use os-auth-strategy=noauth with neutronclient still makes it check with keystone for tokens:

$ neutron --os-auth-strategy=noauth --os-url=http://127.0.0.1:9696 router-list
...,

key-access:
10.35.6.13 - - [30/Sep/2014:08:25:30 -0400] "GET /v2.0 HTTP/1.1" 200 420 "-" "python-keystoneclient"
10.35.6.13 - - [30/Sep/2014:08:25:30 -0400] "POST /v2.0/tokens HTTP/1.1" 200 3990 "-" "python-keystoneclient"

Even though the os-auth-strategy option is deprecated, until removed completely it should definitely work.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/125022
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=2eba58adc16136e0a0d461ce2494a81688c49302
Submitter: Jenkins
Branch: master

commit 2eba58adc16136e0a0d461ce2494a81688c49302
Author: John Schwarz <email address hidden>
Date: Tue Sep 30 15:31:11 2014 +0300

    Don't get keystone session if using noauth

    This patch tells neutronclient not to open an authentication session
    against keystone if using --os-auth-strategy=noauth.

    The intended behaviour in bp keystone-v3-api-support was that
    --os-auth-strategy will be completely deprecated and that the absence
    of --os-auth-url will signify that noauth is needed. This patch does
    not intend to deprecate the strategy option, since that seems to be a
    much larger change in the client, so a smaller fix is proposed instead.

    This is needed for future Neutron integration tests which will be done
    in-tree, since we don't want Neutron to depend on other projects
    (including Keystone) during these tests.

    Closes-bug: #1375765
    Change-Id: I9c61e304f75d3d105e1d66782a7495488eefd5e2