Packstack deployment - Error message and their solution

1.NTP error:

ERROR : Error appeared during Puppet run: 192.168.140.130_chrony.pp

Error: /usr/sbin/ntpdate 192.168.122.130 returned 1 instead of one of [0] [0m

Solution:

Edit answer file

CONFIG_NTP_SERVERS=0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org,3.pool.ntp.org

For more info:

https://bugzilla.redhat.com/show_bug.cgi?id=983771

2.Error in monodb and fix

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

3."packstack --allinone" fails with "Cinder's volume group 'cinder-volumes' could not be created" error message.

Installing dependencies for Cinder...                  [ DONE ]

Checking if the Cinder server has a cinder-volumes vg...[ ERROR ]

ERROR : Cinder's volume group 'cinder-volumes' could not be created

Workaround:

This happens when packstack tries to create the temporary cinder volume group based on loop device. To circumvent this, we can create it upfront and tell packstack not to create it for us when prompted.

Steps to create temporary volume group.

# mkdir -p /var/lib/cinder

# dd if=/dev/zero of=/var/lib/cinder/cinder-volumes bs=1 count=0 seek=20G

# losetup --show -f /var/lib/cinder/cinder-volumes

# pvcreate /dev/loopx

Replace loopx with the output from the previous command.

# vgcreate cinder-volumes /dev/loopx

Run "vgs" command and verify that cinder-volumes volume groups exists.

Then run packstack and specify not to create the temporary volume group for you.

More info: https://access.redhat.com/solutions/437963