Ask Your Question
0

Juno error | packstack

asked 2014-11-19 04:19:50 -0500

pawankkamboj gravatar image

updated 2014-11-19 08:00:22 -0500

smaffulli gravatar image

Getting following error while installing juno on RHEL7.

Adding Glance manifest entries                       [ DONE ]
Adding Cinder Keystone manifest entries              [ DONE ]
Adding Cinder manifest entries                    [ ERROR ]

ERROR : 'CONFIG_CINDER_VOLUMES_SIZE'
Please check log file /var/tmp/packstack/20141119-104030-MOft75/openstack-setup.log for more information

Here is cinder config in answer file.

CONFIG_CINDER_BACKEND=lvm
CONFIG_CINDER_VOLUMES_CREATE=n
CONFIG_CINDER_VOLUMES_SIZE=2G

Packstack rpm details are:

openstack-packstack-puppet-2014.2-0.5.dev1316.g733aa73.el7.centos.noarch
openstack-packstack-2014.2-0.5.dev1316.g733aa73.el7.centos.noarch

Help me on this?

edit retag flag offensive close merge delete
add a comment

4 answers

Sort by ยป oldest newest most voted
0

answered 2014-11-24 05:07:51 -0500

strider gravatar image

updated 2014-12-05 09:56:54 -0500

To perform a Packstack Juno installation with a pre-existing cinder-volumes group, you will need this patch https://review.openstack.org/#/c/136766/ first.

And of course, with:

CONFIG_CINDER_BACKEND=lvm
CONFIG_CINDER_VOLUMES_CREATE=n
CONFIG_CINDER_VOLUMES_SIZE=2G

UPDATE - 2014-12-05

The new rpm builds containing the fix for that issue will be available soon from the official repo.

Meanwhile, you can use them from the copr repo:

edit flag offensive delete link more
add a comment
1

answered 2014-11-24 04:31:12 -0500

Christian Berendt gravatar image

This was a bug in Packstack: https://bugzilla.redhat.com/show_bug.... . It was not possible to use CONFIG_CINDER_VOLUMES_CREATE=n . It should be fixed with https://review.openstack.org/#/c/131803/ and it should now be possible to use CONFIG_CINDER_VOLUMES_CREATE=y.

edit flag offensive delete link more
add a comment
1

answered 2014-11-19 04:51:15 -0500

dbaxps gravatar image

updated 2014-11-19 04:52:17 -0500

You should be able to find answer-file-xxxxxx.txt after failure in your current directory.
Update it 

CONFIG_CINDER_BACKEND=lvm
CONFIG_CINDER_VOLUMES_CREATE=y
CONFIG_CINDER_VOLUMES_SIZE=20G

and rerun packstack --answer-file=./answer-file-xxxxxx.txt

edit flag offensive delete link more
add a comment
0

answered 2014-11-19 04:58:25 -0500

pawankkamboj gravatar image

thanks it works!

edit flag offensive delete link more

Comments

Which answer worked? Please select the correct one. Or add this comment to the correct answer so we can mark this as solved.

mpetason gravatar imagempetason ( 2014-12-08 10:59:55 -0500 )edit
add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

subscribe to rss feed

Stats

Asked: 2014-11-19 04:19:50 -0500

Seen: 413 times

Last updated: Dec 05 '14

Related questions

add a compute node in juno

VNC port not open in firewall

ubuntu cloud-init can't get metadata at boot

Error during rdo installation of icehouse in centOS

High CPU load VPNaaS and libreswan on CentOS 7

Openstack juno's on centOS 6.5

Why does RDO Packstack fail?

tenant and external network vlan mapping

Openstack Juno Keypair Injection failed

instance cannot access from anywhere