Bug 1296844 - RDO Kilo packstack AIO install fails on CentOS 7.2. Error: Unable to connect to mongodb server! (192.169.142.54:27017)
Summary: RDO Kilo packstack AIO install fails on CentOS 7.2. Error: Unable to connect ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: Kilo
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: Kilo
Assignee: Martin Magr
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-08 09:14 UTC by Boris Derzhavets
Modified: 2016-05-19 08:20 UTC (History)
4 users (show)

Fixed In Version: openstack-packstack-8.0.0-0.7.0rc2.el7.noarch
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 08:20:57 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
OpenStack gerrit 181294 None None None 2016-05-19 08:20:57 UTC

Description Boris Derzhavets 2016-01-08 09:14:30 UTC
Description of problem:
Running packstack --allinone get failure

Applying 192.169.142.54_redis.pp
192.169.142.54_mongodb.pp:                        [ ERROR ]          
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 192.169.142.54_mongodb.pp
Error: Unable to connect to mongodb server! (192.169.142.54:27017)

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

[root@ip-192-169-142-54 ~(keystone_admin)]# nova-manage version
2015.1.1-1.el7

[root@ip-192-169-142-54 ~(keystone_admin)]# rpm -qa | grep openstack-packstack
openstack-packstack-puppet-2015.1-0.14.dev1616.g5526c38.el7.noarch
openstack-packstack-2015.1-0.14.dev1616.g5526c38.el7.noarch

How reproducible:

Download rdo-release-kilo-1.noarch.rpm
rpm -iv rdo-release-kilo-1.noarch.rpm
yum -y install openstack-packstack
Run packstack --allinone on CentOS 7.2

Steps to Reproduce:

1. Download rdo-release-kilo-1.noarch.rpm
2. rpm -iv rdo-release-kilo-1.noarch.rpm
3. yum -y install openstack-packstack
4. packstack --allinone ( on CentOS 7.2 )



Actual results:

192.169.142.54_mongodb.pp:                        [ ERROR ]          
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 192.169.142.54_mongodb.pp
Error: Unable to connect to mongodb server! (192.169.142.54:27017)


Expected results:

Successful install

Additional info:

Workaround (to bind to host IP, actually binds to 127.0.0.1 )

systemctl stop mongod.service
rm -f /etc/mongodb.conf
ln -s /etc/mongod.conf /etc/mongodb.conf
Rerun packstack

Comment 1 Boris Derzhavets 2016-01-08 10:15:30 UTC
I attempted patch suggested in
http://arctton.blogspot.com/2015/04/rdo-juno-packstack-deploy-failed-with.html
It doesn't work for me on RDO Kilo, binding to 127.0.0.1 is still in place.

Symlinking mongodb.conf ( workaround ) gives, what is required :-

[root@ip-192-169-142-54 ~]# netstat -antp | grep mongod
tcp        0      0 192.169.142.54:27017    0.0.0.0:*               LISTEN      30470/mongod        
tcp        0      0 192.169.142.54:27017    192.169.142.54:47861    ESTABLISHED 30470/mongod        
tcp        0      0 192.169.142.54:27017    192.169.142.54:47567    ESTABLISHED 30470/mongod        
tcp        0      0 192.169.142.54:27017    192.169.142.54:47488    ESTABLISHED 30470/mongod        
tcp        0      0 192.169.142.54:27017    192.169.142.54:47575    ESTABLISHED 30470/mongod        

[root@ip-192-169-142-54 ~]# ps -ef | grep 30470
mongodb  30470     1  0 11:47 ?        00:00:07 /usr/bin/mongod --quiet -f /etc/mongodb.conf run
[root@ip-192-169-142-54 ~]#

Comment 3 Javier Peña 2016-05-19 08:20:57 UTC
There were a number of patches to clean up the mongodb configuration, caused by packaging differences between RDO and Red Hat OpenStack Platform (the latest one was https://review.openstack.org/181294). This is currently known to work properly with RDO Mitaka, so I'm closing the bug as CURRENTRELEASE.

Please feel free to reopen the bug if the issue is still relevant in the current RDO release.


Note You need to log in before you can comment on or make changes to this bug.