Ask Your Question

has anyone achieved in getting a working Icehouse with packstack --allinone

asked 2014-08-15 08:43:03 -0500

D43m0n gravatar image

updated 2014-08-15 12:35:11 -0500

rbowen gravatar image

Bear with me please, I'm very enthusiastic about what openstack has to offer, the idea behind it and why it was founded. I'm struggling the last few weeks to get openstack installed with packstack's --allinone method. If, and I really do mean if an installation succeeds, I get a allinone that can sometimes not even create an image with glance (either via dashboard, or via the cli), but when that sometimes works, I can't even get an instance running, because it's stuck at spawning.

I've tried reinstalling completely from scratch several times, following the RDO quick start to the letter but having different results all the time doesn't exactly make me feel either packstack is ready for public use, or the current Icehouse release is still very much in development.

Is it just me, or my setup, my hardware, my configuration (even with --allinone)?

some details of my setup and how I start (from scratch all the time):

I'm running on a 5 year old HP DL380 G5 with 8 GB RAM and a quad core Intel(R) Xeon(R) CPU E5440 @ 2.83GHz on a 72GB SmartArray P400 RAID-controller. The OS I'm installing is RHEL 6.5 and is fully up to date before I start adding the packstack repositories. My installation method is as follows:

  1. I PXE-boot the server and supply a kickstart file which in post installs a puppet client
  2. the puppet client registers itself on the puppetmaster which uses an External Node Configuration with The Foreman.
  3. In the Foreman, I assign a so called Host Group which bundles a specific set of puppet modules and classes which do nothing more than adding a few users, their SSH-keys, add a few packages, do some basic configuration of sudo, ntp, DNS and that's it.
  4. To make sure my puppet installation doesn't interfere with packstack's method, I uninstall puppet, the puppetlabs repo, remove any cron items that restart the puppet agent in case it died and do a yum update -y to install the latest versions.
  5. I then add the RDO repositories using sudo yum install -y
  6. I then install the packstack installer using sudo yum install -y openstack-packstack
  7. when that's done, I start packstack as follows: sudo packstack --allinone

What happens next is hardly ever the same. Packstack might fail on several items, sometimes on mysql.pp, sometimes on provision_demo.pp. But it might also succeed, but then it might not even complete image creation with glance, but when that does, it'll keep an instance on "spawning" forever.

I have no intention of being negative, kicking someone's knees but I'm having serious doubts about either packstack or openstack. And honestly, this is not my first encounter with open source or Linux administration.

Before I start posting and updating a lot of information, am I alone in this experience?

edit retag flag offensive close merge delete

4 answers

Sort by » oldest newest most voted

answered 2014-08-15 12:38:52 -0500

rbowen gravatar image

There are a number of workarounds listed on the Workarounds page that you should have a look at before you try again, or when you encounter errors during the installation. That page should be up to date with the current state of the packages, but if there are things missing, please do let me know so that we can update it.

edit flag offensive delete link more


thanks, according to (this) guide I figured out the ip netns gave me a wrong result. That's worth mentioning, since it's not listed on the (Workarounds) page. Neutron is not responding now.

D43m0n gravatar imageD43m0n ( 2014-08-17 12:54:02 -0500 )edit

answered 2014-08-15 09:25:28 -0500

dbaxps gravatar image

updated 2014-08-15 12:39:46 -0500

rbowen gravatar image

My experience with RDO IceHouse on CentOS 7

# yum install -y
# yum install -y openstack-packstack
# packstack --allinone
Apply workaround :-

Installed several times on CentOS 7 with no problems.
Multi Node installations via packstack ( no Foreman involvment )
1. RDO Setup Two Real Node (Controller+Compute) IceHouse Neutron ML2&OVS&VXLAN Cluster on CentOS 7
2. Setup Gluster 3.5.2 on Two Node Controller&Compute Neutron ML2&VXLAN&OVS CentOS 7 Cluster
Regarding RDO (pure packstack approach) multi-node IceHouse installs on Fedora 20, view
Showing headlines posted by dba477

edit flag offensive delete link more

answered 2014-08-15 09:04:25 -0500

beni gravatar image

I didn't have problems with image creation or instances keep “spawning”. For me the network was more the problem. You might want to follow this guide that uses packstack options to suppress the creation of the demo user and network. I had problems with the demo network but when I created a network manually after the packstack run, it was fine.

I use Scientific Linux 6.5. The commands posted on http://information-technology.web.cer... were helpful for me to prepare the system before running Packstack. They avoid some of the typical fails, like the MySQL one. I don't know if they all apply for RHEL 6.5.

edit flag offensive delete link more


Thank you, I will give that a try. I also found your question regarding running the packstack installation not as root. If that's important, then that is at least a very important bit that's missing on the quick start guide.

D43m0n gravatar imageD43m0n ( 2014-08-15 09:12:15 -0500 )edit

Actually I gave up running Packstack as normal user as the SSH issues I mentioned in my question annoyed me too much; and I think running Packstack as root will not lead to problems like the ones you describe in your question.

beni gravatar imagebeni ( 2014-08-15 09:28:08 -0500 )edit

That's funny, I ran all the commands as the root user in the last few attempts. Even on the console instead of screen in a ssh session. Following your suggestion, I already stumbled upon a needed fix.

D43m0n gravatar imageD43m0n ( 2014-08-15 09:45:12 -0500 )edit

I'm following the (All-in-One DIY) guide and am now at the the step to create an external network with neutron net-create extnet --router:external=True. But nothing happens. It just sits there. No error in /var/log/neutron/*.log

D43m0n gravatar imageD43m0n ( 2014-08-17 12:51:27 -0500 )edit

What do you mean with “sits there”? Did you source the RC file for the admin user (keystonerc_admin after a installation with Packstack)? Check openstack-status | less to see if Neutron and the other OpenStack services are running.

beni gravatar imagebeni ( 2014-08-17 15:13:16 -0500 )edit

answered 2014-08-18 10:17:47 -0500

D43m0n gravatar image

So far, after trying several RDO guides with packstack and following tutorials, watching video's I'd have to conclude my question is answered by the absence of answer. Despite packstacks good intentions, I find it not upholding Red Hat's quality I've come to know the last 8 years. Sorry.

edit flag offensive delete link more


OK, I've just subscribed to a 60-day trial of Red Hat's production version of (Openstack). I'm just curious to see what happens.

D43m0n gravatar imageD43m0n ( 2014-08-19 07:00:23 -0500 )edit

Well... the Red Hat production version behaves the same. Whenever I try to change/add/launch/import something in the dashboard, I get a white box with a spinning wheel and the text "Working" on a dark background. I've filed a support case at Red Hat. I must be doing something wrong...

D43m0n gravatar imageD43m0n ( 2014-08-20 02:06:46 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-08-15 08:43:03 -0500

Seen: 1,662 times

Last updated: Aug 15 '14