Neutron uses the Nova API public endpoint which may not be always reachable from the node running the Neutron service
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-neutron |
Fix Released
|
Undecided
|
Brent Eagles | ||
tripleo |
Fix Released
|
High
|
Brent Eagles |
Bug Description
Originally reported https:/
Neutron uses the Nova API public endpoint which may not be always reachable from the node running the Neutron services. We could instead the internal endpoint as this should be reachable from nodes which don't have access to the public endpoint network.
Scenario where this issue could show up:
Neutron API services are running on a different role than the controller running HAProxy where the public endpoints are binding. The Neutron role is not connected to the OSP-d External network since it runs internal only services and outgoing traffic to the External network from this role nodes is not allowed.
Version-Release number of selected component (if applicable):
openstack-
How reproducible:
100%
Steps to Reproduce:
1. Deploy overcloud
2. Check /etc/neutron/
Actual results:
[nova]
#
# From neutron
#
# Name of nova region to use. Useful if keystone manages more than one region.
# (string value)
#region_name = <None>
# Type of the nova endpoint to use. This endpoint will be looked up in the
# keystone catalog and should be one of public, internal or admin. (string
# value)
# Allowed values: public, admin, internal
#endpoint_type = public
Expected results:
endpoint_type = internal
tags: | added: pike-backport-potential |
Changed in tripleo: | |
milestone: | rocky-1 → queens-rc1 |
Changed in puppet-neutron: | |
status: | In Progress → Fix Released |
We aren't configuring this at all at the moment so the current value reflects the neutron's default value.