Bug 1438795

Summary: ceilometer-wsgi in list of processes when passing enable_legacy_ceilometer_api = False in undercloud.conf
Product: Red Hat OpenStack Reporter: Sasha Smolyak <ssmolyak>
Component: instack-undercloudAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED ERRATA QA Contact: Sasha Smolyak <ssmolyak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 11.0 (Ocata)CC: jruzicka, jschluet, mburns, pkilambi, rhel-osp-director-maint, srevivo
Target Milestone: rcKeywords: Triaged
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: instack-undercloud-6.0.0-6.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-17 20:17:37 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:

Description Sasha Smolyak 2017-04-04 12:37:47 UTC
Description of problem:
ceilometer-wsgi in list of undercloud processes when passing enable_legacy_ceilometer_api  = False in undercloud.conf

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

How reproducible:

Steps to Reproduce:
1. add enable_legacy_ceilometer_api  = False to undercloud.conf
2. Deploy undercloud
3. Observe list of httpd processes

Actual results:
ceilometer_wsgi is in the list

Expected results:
The process is not supposed to be there

Additional info:
Get a CRITICAL error in undercloud app.log:
CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Unable to establish connection to HTTPSConnectionPool(host='', port=35357): Max retries exceeded with url
: / (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7f55f3875190>: Failed to establish a new connection: [Errno 111] Connection refused',))

Need to verify it doesn't appear once the problem is fixed

Comment 3 Sasha Smolyak 2017-04-23 07:24:20 UTC
VErified, doesn't happen anymore. No errors in log as well.

Comment 4 errata-xmlrpc 2017-05-17 20:17:37 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.