Ask Your Question

Howto setup centos for packstack with (stable) Kilo release

asked 2016-01-07 08:36:29 -0500

theque42 gravatar image


I've been trying to wrap my head around openstack and the packstack concept of installation, in my success is quite ...intermittent :-(

I feel its not quite clear which repositories I should install/enable/disable/remove or something similar, depending on if I use fedora 22 or CentOS 7. One note says I NEED epel-repositories, and then I see the command "yum --disable epel-release" flashing past on the screen during packstack install.

But mainly, I'd like to know how I can specifically STAY within a specific release of Openstack, even when reinstalling, once in a while. Using the "rdo-releaserpm" repository always(?) points to the latest versions, and right *now, since liberty rdo/packstack installations fail 100%(cinder volume quota issues), I would like to attempt to back down to kilo, instead of liberty.

So if someone could easily indicate which - IF ANY - additional repositories I should add to a fresh install of CentOS 7 (or fedora 22 if you want, but I was told centos is a safer bet?!?), and how to ensure that I get the kilo release, I would be very thankful. Should I for instance use "--use-epel=y" to enforce those repositories?

I have tried with "", but that version consistently seems to fail installation.....

Btw. I am using a snapshotted fedora/centos VM, that I simply revert to its starting position every time I install, and this VM has worked fine for other installations with packstack. Its just that of the 50 or so runs I've dont with packstack, on the same VM...i think I've succeeded about 5...maybe ten times.


edit retag flag offensive close merge delete


First of, my true goal is to set up a X-split system with controller, 1 neutron, and 2+ compute nodes. I just test --allinone as a startingpoint. My current failure when running packstack is:

theque42 gravatar imagetheque42 ( 2016-01-08 08:35:36 -0500 )edit

ERROR : Error appeared during Puppet run: Error: Could not autoload puppet/provider/vs_port/ovs_redhat_el6: Could not find parent provider ovs_redhat of ovs_redhat_el6.

And this is an error I get quite often in my reinstalls.

theque42 gravatar imagetheque42 ( 2016-01-08 08:35:39 -0500 )edit

3 answers

Sort by ยป oldest newest most voted

answered 2016-01-07 09:07:02 -0500

Hi, RDO repos are hosted here:

If you find any error on installation, please, check this ask for a previous answered issue. If not answered before, open a new question.


edit flag offensive delete link more

answered 2016-01-07 09:47:47 -0500

dbaxps gravatar image

updated 2016-01-08 08:05:09 -0500

UPDATE 01/08/2015
Dirty fix

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


image description

theque42 wrote : Wrong statement? You comment indicates precisely the whole issue "I had to disable nagios last time".
Addressing his last statement
Hackery setting up RDO Kilo on CentOS 7.2 with Mongodb up and running as of 01/08/2015

You wrote "I have tried with "", but that version consistently seems to fail installation..... "
It' s wrong statement.

On yum updated CentOS 7.2
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 --gen-answer-file answerAIO.txt
5. I had to disable nagios last time, to have nagios running see hack in UPDATE section
6. packstack --answer-file=./answerAIO.txt

EPEL 7 will be enabled by packstack run.

edit flag offensive delete link more


Wrong statement? You comment indicates precisely the whole issue "I had to disable nagios last time". That's just the problem, isnt it? What you have to disable/change/modify/add/magically-figure-out-without-any-hints-whatsoever, changes on an hourly basis...

theque42 gravatar imagetheque42 ( 2016-01-07 10:36:35 -0500 )edit

I don't track Bugzilla , just try with nagios. It might be already fixed. RDO is community driven. Fix nagios puppet , if you need it so much. Troubleshoot issue on your own and file BUG upstream either purchase RHOS 7. You got exactly what you payed for.

dbaxps gravatar imagedbaxps ( 2016-01-07 13:11:52 -0500 )edit

Yes, it seems to be an issue not for you only. Failure to connect to mongodb && XX_mongodb.pp failure. There are complains on the Net. Content of logs is not quite clear. Fixing mongo.pp with correct version 7.2 doesn't help.

dbaxps gravatar imagedbaxps ( 2016-01-07 17:01:54 -0500 )edit

answered 2016-01-11 14:27:11 -0500

Sandeep gravatar image

as per screenshot it looks very simple issue only need to stop Network manager and re-execute packstack. service NetworkManager stop .

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-01-07 08:36:29 -0500

Seen: 1,950 times

Last updated: Jan 11 '16