yahoo-eng-team team mailing list archive

Thread
Date
[Bug 1371716] [NEW] nova endpoints returns endpoints from the wrong region when region is set

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Matt Fischer <matt@xxxxxxxxxxxxxxx>
Date: Fri, 19 Sep 2014 17:35:16 -0000
Reply-to: Bug 1371716 <1371716@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Public bug reported:

We have two regions in our environment. When OS_REGION_NAME is set to
"WEST" and I run nova endpoints, I get endpoints back for EAST. The
keystone CLI does the correct thing and returns endpoints matching the
region.

The east region comes first in our endpoint list which I assume is the
logic that its using.

Here's some sample output from nova endpoints and keystone catalog.

OS_REGION_NAME=WEST nova endpoints
+-------------+-----------------------------------------------------+
| keystone    | Value                                               |
+-------------+-----------------------------------------------------+
| adminURL    | http://east.example.com:35357/v2.0   |
| id          | 503fc143506c44fb876ffe4fa82497d6                    |
| internalURL | http://east.example.com:5000/v2.0 |
| publicURL   | http://east.example.com:5000/v2.0          |
| region      | EAST                                                 |
+-------------+-----------------------------------------------------+

OS_REGION_NAME=WEST keystone catalog
Service: identity
+-------------+-----------------------------------------------------+
|   Property  |                        Value                        |
+-------------+-----------------------------------------------------+
|   adminURL  |  http://west.example.com:35357/v2.0  |
|      id     |           16937fc883eb4fc9968b8e1b42a30a70          |
| internalURL | http://west.example.com:5000/v2.0 |
|  publicURL  |      http://west.example.com:5000/v2.0     |
|    region   |                        WEST                         |
+-------------+-----------------------------------------------------+

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

  We have two regions in our environment. When OS_REGION_NAME is set to
  "WEST" and I run nova endpoints, I get endpoints back for EAST. The
  keystone CLI does the correct thing and returns endpoints matching the
  region.
  
  Here's some sample output from nova endpoints and keystone catalog.
  
  OS_REGION_NAME=WEST nova endpoints
  +-------------+-----------------------------------------------------+
  | keystone    | Value                                               |
  +-------------+-----------------------------------------------------+
  | adminURL    | http://east.example.com:35357/v2.0   |
  | id          | 503fc143506c44fb876ffe4fa82497d6                    |
  | internalURL | http://east.example.com:5000/v2.0 |
  | publicURL   | http://east.example.com:5000/v2.0          |
  | region      | EAST                                                 |
  +-------------+-----------------------------------------------------+
  
  OS_REGION_NAME=EAST keystone catalog
  Service: identity
  +-------------+-----------------------------------------------------+
  |   Property  |                        Value                        |
  +-------------+-----------------------------------------------------+
  |   adminURL  |  http://west.example.com:35357/v2.0  |
  |      id     |           16937fc883eb4fc9968b8e1b42a30a70          |
  | internalURL | http://west.example.com:5000/v2.0 |
  |  publicURL  |      http://west.example.com:5000/v2.0     |
- |    region   |                         NCW                         |
+ |    region   |                        WEST                         |
  +-------------+-----------------------------------------------------+

** Description changed:

  We have two regions in our environment. When OS_REGION_NAME is set to
  "WEST" and I run nova endpoints, I get endpoints back for EAST. The
  keystone CLI does the correct thing and returns endpoints matching the
  region.
  
  Here's some sample output from nova endpoints and keystone catalog.
  
  OS_REGION_NAME=WEST nova endpoints
  +-------------+-----------------------------------------------------+
  | keystone    | Value                                               |
  +-------------+-----------------------------------------------------+
  | adminURL    | http://east.example.com:35357/v2.0   |
  | id          | 503fc143506c44fb876ffe4fa82497d6                    |
  | internalURL | http://east.example.com:5000/v2.0 |
  | publicURL   | http://east.example.com:5000/v2.0          |
  | region      | EAST                                                 |
  +-------------+-----------------------------------------------------+
  
- OS_REGION_NAME=EAST keystone catalog
+ OS_REGION_NAME=WEST keystone catalog
  Service: identity
  +-------------+-----------------------------------------------------+
  |   Property  |                        Value                        |
  +-------------+-----------------------------------------------------+
  |   adminURL  |  http://west.example.com:35357/v2.0  |
  |      id     |           16937fc883eb4fc9968b8e1b42a30a70          |
  | internalURL | http://west.example.com:5000/v2.0 |
  |  publicURL  |      http://west.example.com:5000/v2.0     |
  |    region   |                        WEST                         |
  +-------------+-----------------------------------------------------+

** Description changed:

  We have two regions in our environment. When OS_REGION_NAME is set to
  "WEST" and I run nova endpoints, I get endpoints back for EAST. The
  keystone CLI does the correct thing and returns endpoints matching the
  region.
+ 
+ The east region comes first in our endpoint list which I assume is the
+ logic that its using.
  
  Here's some sample output from nova endpoints and keystone catalog.
  
  OS_REGION_NAME=WEST nova endpoints
  +-------------+-----------------------------------------------------+
  | keystone    | Value                                               |
  +-------------+-----------------------------------------------------+
  | adminURL    | http://east.example.com:35357/v2.0   |
  | id          | 503fc143506c44fb876ffe4fa82497d6                    |
  | internalURL | http://east.example.com:5000/v2.0 |
  | publicURL   | http://east.example.com:5000/v2.0          |
  | region      | EAST                                                 |
  +-------------+-----------------------------------------------------+
  
  OS_REGION_NAME=WEST keystone catalog
  Service: identity
  +-------------+-----------------------------------------------------+
  |   Property  |                        Value                        |
  +-------------+-----------------------------------------------------+
  |   adminURL  |  http://west.example.com:35357/v2.0  |
  |      id     |           16937fc883eb4fc9968b8e1b42a30a70          |
  | internalURL | http://west.example.com:5000/v2.0 |
  |  publicURL  |      http://west.example.com:5000/v2.0     |
  |    region   |                        WEST                         |
  +-------------+-----------------------------------------------------+

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1371716

Title:
  nova endpoints returns endpoints from the wrong region when region is
  set

Status in OpenStack Compute (Nova):
  New

Bug description:
  We have two regions in our environment. When OS_REGION_NAME is set to
  "WEST" and I run nova endpoints, I get endpoints back for EAST. The
  keystone CLI does the correct thing and returns endpoints matching the
  region.

  The east region comes first in our endpoint list which I assume is the
  logic that its using.

  Here's some sample output from nova endpoints and keystone catalog.

  OS_REGION_NAME=WEST nova endpoints
  +-------------+-----------------------------------------------------+
  | keystone    | Value                                               |
  +-------------+-----------------------------------------------------+
  | adminURL    | http://east.example.com:35357/v2.0   |
  | id          | 503fc143506c44fb876ffe4fa82497d6                    |
  | internalURL | http://east.example.com:5000/v2.0 |
  | publicURL   | http://east.example.com:5000/v2.0          |
  | region      | EAST                                                 |
  +-------------+-----------------------------------------------------+

  OS_REGION_NAME=WEST keystone catalog
  Service: identity
  +-------------+-----------------------------------------------------+
  |   Property  |                        Value                        |
  +-------------+-----------------------------------------------------+
  |   adminURL  |  http://west.example.com:35357/v2.0  |
  |      id     |           16937fc883eb4fc9968b8e1b42a30a70          |
  | internalURL | http://west.example.com:5000/v2.0 |
  |  publicURL  |      http://west.example.com:5000/v2.0     |
  |    region   |                        WEST                         |
  +-------------+-----------------------------------------------------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1371716/+subscriptions
Follow ups

[Bug 1371716] Re: nova endpoints returns endpoints from the wrong region when region is set
From: Sean Dague, 2014-09-19
[Bug 1371716] [NEW] nova endpoints returns endpoints from the wrong region when region is set
From: Matt Fischer, 2014-09-19
References

[Bug 1371716] [NEW] nova endpoints returns endpoints from the wrong region when region is set
From: Matt Fischer, 2014-09-19