Bug 1525427

Summary: [RHOSP10] nova --bypass-url flag throw the ERROR (KeyError): 'versions'
Product: Red Hat OpenStack Reporter: Rajesh Tailor <ratailor>
Component: python-novaclientAssignee: Rajesh Tailor <ratailor>
Status: CLOSED ERRATA QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: low    
Version: 10.0 (Newton)CC: berrange, dasmith, eglynn, jhakimra, jruzicka, kchamart, lyarwood, mlopes, mnadeem, ratailor, sbauza, sferdjao, sgordon, slinaber, srevivo, vromanso
Target Milestone: z7Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-novaclient-6.0.2-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1517264 Environment:
Last Closed: 2018-02-27 16:24:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1517264    
Bug Blocks:    

Description Rajesh Tailor 2017-12-13 10:20:40 UTC 
+++ This bug was initially created as a clone of Bug #1517264 +++

Description of problem:

While executing the any nova command with --bypass-url, it throw the error ERROR (KeyError): 'versions'. After analyzing a bit, i come to know the below parameter set wrong. 

response_key get sets to "versions" where as it gets set to "servers" when execute without --bypass-url and produce the expected output.

>> /usr/lib/python2.7/site-packages/novaclient/base.py +246
    
$nova --version
3.3.2

 
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
[stack@instack ~]$ nova --bypass-url http://192.168.124.20:8774/v2.1/  list

ERROR (KeyError): 'versions'


Expected results:
It should produce the expected output of nova list

Additional info:
Comment 1 Rajesh Tailor 2017-12-13 10:22:39 UTC 
*** Bug 1525424 has been marked as a duplicate of this bug. ***
Comment 11 errata-xmlrpc 2018-02-27 16:24:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0369