Network client (neutron) initialized without specifying region

Can you please provide debug output and configuration information?

I just uploaded patch for review. Think it will be linked soon.

Why does bot did't link review?

I'm not sure why it wasn't added: https://review.openstack.org/#/c/306584/

Reviewed: https://review.openstack.org/306584
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=8c6b5a087a4b0dca16faffdbcb5fc9f2d424ddf8
Submitter: Jenkins
Branch: master

commit 8c6b5a087a4b0dca16faffdbcb5fc9f2d424ddf8
Author: Andrey Larionov <email address hidden>
Date: Fri Apr 15 21:23:20 2016 +0300

    Initialize neutron client with region name

    All clients except neutron are initialized with region name.
    This makes unable to use network related commands of
    openstackclient in multi-region configurations

    Change-Id: I200dc9a2f938c3e69357f91c79810df167e4fccb
    Closes-bug: 1570491

Do you have any estimation on release date, which includes this fix?

There should hopefully be a release this week.

This issue was fixed in the openstack/python-openstackclient 2.4.0 release.

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/329419

Change abandoned by Stuart McLaren (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/329419

Ubuntu SRU details:

[Description]
The newInitialize neutron client with region name

The openstack client initializes all clients except neutron with the region name. This prevents openstack client from using network related commands in multi-region deployments.

[Test Case]
Deploy a multi-region cloud and use the openstack client against it. The first network service is selected.

[Regression Potential]
Low. This is a small bug fix that is being backported from version 2.4.0 to 2.3.1.

This has been uploaded to the unapproved queue for xenial [1] and is ready for SRU review.

[1] https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=

Hello Andrey, or anyone else affected,

Accepted python-openstackclient into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python-openstackclient/2.3.1-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Regression testing on xenial-proposed has completed successfully for this. We performed regression testing by juju deploying two openstack clouds, one against -proposed and one against -updates, and running tempest integration smoke tests[1] to verify those deployed clouds, evaluating any differences in results. [1] https://github.com/openstack/tempest/blob/master/README.rst

Also tested manually on xenial-proposed with invalid endpoint in RegionTwo: http://paste.ubuntu.com/25283922/

Also tested manually on trusty-mitaka-proposed with invalid endpoint in RegionTwo: http://paste.ubuntu.com/25283954/

This bug was fixed in the package python-openstackclient - 2.3.1-0ubuntu1

---------------
python-openstackclient (2.3.1-0ubuntu1) xenial; urgency=medium

  * d/gbp.conf: Update for stable/mitaka branch.
  * New upstream point release (LP: #1703372).
  * d/p/init-neutron-client-with-region-name.patch: Initialize neutron
    client with region name to enable use with multi-region deployments
    (LP: #1570491).

 -- Corey Bryant <email address hidden> Mon, 10 Jul 2017 09:42:46 -0400

The verification of the Stable Release Update for python-openstackclient has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

The verification of the Stable Release Update for python-openstackclient has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package python-openstackclient - 2.3.1-0ubuntu1~cloud0
---------------

 python-openstackclient (2.3.1-0ubuntu1~cloud0) trusty-mitaka; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 python-openstackclient (2.3.1-0ubuntu1) xenial; urgency=medium
 .
   * d/gbp.conf: Update for stable/mitaka branch.
   * New upstream point release (LP: #1703372).
   * d/p/init-neutron-client-with-region-name.patch: Initialize neutron
     client with region name to enable use with multi-region deployments
     (LP: #1570491).