python-mistralclient

Region is not used when coming from openstackclient

Bug #1779705 reported by Pierre Gaxatte
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-mistralclient
Fix Committed
Undecided
Quentin GROLLEAU

Bug Description

In a multi-region environment, the mistral client correctly uses the region put in OS_REGION_NAME but not when using the openstack client.

The call is made to the first endpoint found in the catalog.

Revision history for this message
Quentin GROLLEAU (quentin.grolleau) wrote :

If you do a :

openstack workflow list

and you have several regions

It will chose the first one in the endpoint list

HTTPSConnectionPool(host='mistral', port=8989): Max retries exceeded with url: /v2/workflows (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7f3007f610d0>: Failed to establish a new connection: [Errno 111] Connection refused',))

Revision history for this message
Quentin GROLLEAU (quentin.grolleau) wrote :

Or just this output :

("bad handshake: SysCallError(110, 'ETIMEDOUT')",)

Fixing with : https://review.openstack.org/#/c/579612/

Quentin GROLLEAU (quentin.grolleau)
Changed in python-mistralclient:
assignee: nobody → Quentin GROLLEAU (quentin.grolleau)
status: New → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-mistralclient 3.6.1

This issue was fixed in the openstack/python-mistralclient 3.6.1 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.