Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1168690

Summary: Ceilometer cannot connect to MongoDB on db-sync
Product: Red Hat OpenStack Reporter: Jiri Stransky <jstransk>
Component: openstack-foreman-installerAssignee: Jason Guiditta <jguiditt>
Status: CLOSED ERRATA QA Contact: Alexander Chuzhoy <sasha>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.0 (Juno)CC: augol, dmacpher, jstransk, mburns, morazi, rhos-maint, sasha, yeylon
Target Milestone: gaKeywords: TestOnly
Target Release: Installer   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Ceilometer configuration on Controller nodes would not complete due to connection problems with MongoDB while doing db-sync. This fix corrects the MongoDB connectivity and Ceilometer's db-sync now completes successfully.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-09 15:16:43 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:
Attachments:
Description Flags
Puppet log when it reported error status on controller hosts
none
Puppet log when it reported success status on controller hosts (but it still wasn't able to do db-sync) none

Description Jiri Stransky 2014-11-27 15:37:26 UTC 
Description of problem:
On one of Sasha's deployment we hit an issue where Ceilometer wasn't able to connect to MongoDB while doing db-sync on one of the controller hosts. On other controller hosts it seems that the same error was encountered on db-sync, but the Puppet runs finished successfully without skipping. Will attach both error and success logs.

Version-Release number of selected component (if applicable):
openstack-foreman-installer-3.0.2-1.el7ost.noarch
Comment 1 Jiri Stransky 2014-11-27 15:40:55 UTC 
Created attachment 962128 [details]
Puppet log when it reported error status on controller hosts
Comment 2 Jiri Stransky 2014-11-27 15:41:42 UTC 
Created attachment 962130 [details]
Puppet log when it reported success status on controller hosts (but it still wasn't able to do db-sync)
Comment 8 Mike Burns 2014-12-04 15:00:40 UTC 
This is likely fixed by existing fixes for other issues.  Moving to ON_QA to verify.
Comment 10 Alexander Chuzhoy 2014-12-16 23:19:50 UTC 
Verified:
Environment:
openstack-foreman-installer-3.0.6-1.el7ost.noarch
ruby193-rubygem-staypuft-0.5.6-1.el7ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch
rhel-osp-installer-client-0.5.3-1.el7ost.noarch
openstack-puppet-modules-2014.2.7-2.el7ost.noarch
rhel-osp-installer-0.5.3-1.el7ost.noarch



No related errors in the log/report.
The deployment completed successfully.
Comment 12 errata-xmlrpc 2015-02-09 15:16:43 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-2015-0156.html