Bug 1293647 - os-endpoint-type parameter is broken for OSP 6 neutron client
Summary: os-endpoint-type parameter is broken for OSP 6 neutron client
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-neutronclient
Version: 6.0 (Juno)
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
: 6.0 (Juno)
Assignee: Bernard Cafarelli
QA Contact: Alexander Stafeyev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-22 14:38 UTC by Matt Flusche
Modified: 2019-09-12 09:38 UTC (History)
6 users (show)

Fixed In Version: python-neutronclient-2.3.9-3.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, an incompatibility with keystoneclient v3 caused some parameters to be ignored. Now, the keyword argument `endpoint_type` has been replaced with `interface`, resolving this issue.
Clone Of:
Environment:
Last Closed: 2017-06-14 15:43:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1448 0 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2017-06-14 19:29:57 UTC

Description Matt Flusche 2015-12-22 14:38:02 UTC 
Description of problem:

OSP 6 neutron client seems to be impacted by this bug.  I would like to get this reviewed for backporting to address.

https://review.openstack.org/#/c/121047/


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

python-neutronclient-2.3.9-1.el7ost.noarch

How reproducible:
100%


Steps to Reproduce:
1.neutron --os-endpoint-type internalURL --debug net-list (where internalURL is different from publicURL)
2.
3.

Actual results:
uses publicURL for neutron client request

Expected results:
should use internalURL for neutron client request

Additional info:
I've tested this change and it addresses the issue in OSP 6
Comment 1 Assaf Muller 2016-06-07 23:11:05 UTC 
Confirmed to exist in OSP 7+ but missing in OSP 6, simple backport request.
Comment 5 errata-xmlrpc 2017-06-14 15:43:28 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/RHBA-2017:1448
Note You need to log in before you can comment on or make changes to this bug.