Bug 1301126

Summary:	In IPv6 deployments the ceilometer compute agent cannot reach the public endpoint
Product:	Red Hat OpenStack	Reporter:	Giulio Fidente <gfidente>
Component:	openstack-puppet-modules	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED ERRATA	QA Contact:	Marius Cornea <mcornea>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	dnavale, emacchi, gfidente, jguiditt, mburns, mcornea, rhel-osp-director-maint, yeylon
Target Milestone:	z4	Keywords:	ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-puppet-modules-2015.1.8-45.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1301056	Environment:
Last Closed:	2016-02-18 16:44:49 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:
Bug Depends On:
Bug Blocks:	1301056

Description Giulio Fidente 2016-01-22 16:37:08 UTC

+++ This bug was initially created as a clone of Bug #1301056 +++

Description of problem:
In IPv6 deployments the ceilometer compute agent cannot reach the public endpoint so it fails with errors like:
 ConnectionError: ('Connection aborted.', gaierror(-2, 'Name or service not known'))

Since the compute nodes can only reach the isolated network and don't have a means to reach the public endpoint we should switch the os_endpoint_type in /etc/ceilometer/ceilometer.conf to internalURL which can be reachable via the internal_api network.

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-0.8.6-111.el7ost.noarch

How reproducible:
100% 

Steps to Reproduce:
1. Deploy ipv6 enable overcloud
2. Check /var/log/ceilometer/compute.log

Actual results:
ConnectionError: ('Connection aborted.', gaierror(-2, 'Name or service not known'))

Expected results:
There are no errors reported.

Comment 4 errata-xmlrpc 2016-02-18 16:44:49 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://rhn.redhat.com/errata/RHBA-2016-0265.html