Heat templates with cinder volumes

While trying to launch several VMs using heat templates on RHEL OpenStack Liberty only 2 out of 8 launched. Rest failed because cinder volumes could not be created. 

heat stack status was CREATE_FAILED and cinder volume status was error


For a brief moment there was some log on a console related to haproxy failure

While checking the services I noticed that both haproxy and swift-proxy are not running so just decided to restart them

systemctl restart haproxy.service

systemctl start openstack-swift-proxy.service

After that I could again create cinder volumes via heat templates. So be careful – create VMs from templates with cinder one by one

Accessing cloud images

For both Fedora and Ubuntu cloud images we can access them using ssh public key generated during bootup.

Key can be obtained from a console log:

  • Horizon -> Instances -> <fedora_ubuntu_instance> -> Console -> View Full Console Log
  • sudo vim /var/lib/nova/instances/<instance_id>/console.log

SSH can be done from from a proper ip namespace on compute nodes:

Or from any different host if Public IP is associated with the instance.

Nova installation on OpenSUSE 13.1

  • Firewall rules can be modified from GUI:
  • Assign internal interfaces to “Internal zone”
  • Add SSH service to “External zone”

In order to allow to access rabbitmq from a remote (and local) host to rabbitmq server before starting rabbitmq-server add in /etc/rabbitmq/rabbitmq.config:

Instance creation fails with “Cannot find suitable CPU” on Debian 7

KVM by default does not work (even though vmx/smx is enabled for CPUs) – instance creation fails with “Cannot find suitable CPU”.


  • In /etc/libvirtd/qemu.conf:
  • remove file /var/cache/libvirt/qemu/capabilities and restart host (libvirtd restart does not suffice)
  • After restart check capabilities with:

VNC and firewalld on Centos 7 compute node

By default firewalld service is enabled and may cause troubles in accessing via VNC to instances running on Centos compute node.


By default zone=public is used, so it is enough just to add 5900/5901 ports or/and vnc-server service to this zone:


Nova installation on Centos 7


After starting rabbitmq-server service it is not possible to change password using:


In file /etc/systemd/system/multi-user.target.wants/rabbitmq-server.service change

to – add sudo

And restart rabbitmq-server:


Nova incompatibility

Packages for nova which are downloaded with yum contain nova version which is incomaptible with that is running on controller node (Ubuntu):

Controller (Ubuntu 14.04):

Compute (Centos 7):

Problem is described here:

Install packages from EPEL repo manually (only 3 days older):


Packages to install:

I had to forcefully install them using rpm -ivh –force then I restarted openstack-nova-compute service.
After this instances spawned correctly, yet I could not reach them (iptables rules missing, so I disabled iptables).

DHCP addresses got distributed to the instances correctly and I could reach internet from them via my Ubuntu-AIO which acts as a gateway to the internet as well.

Trove installation on Ubuntu 14.04

When installing Trove service on Ubuntu 14.04 I encountered a problem with dependencies not met between Trove related packages. 

Thus the following packages were installed manually with dpkg -i <package_name>

In order to make apt-get still working after manual package installation (which does not check dependencies) it is a must failed dependecies for manually installed packages

In /var/lib/dpkg/status, for each package for which there is a missing dependency just remove it (lsb-base (>= 4.1+Debian11ubuntu7)) from line in the status file:

If there is any config file missing in /etc/trove then download it from: 




In order to use RabbitMQ the following line must be added in

  • trove.conf
  • trove-conductor.conf
  • trove-taskmanager.conf

Instead of (as per manual):

Swift AIO

OpenStack installation instructions from openstack.org assume 3 node architecture therefore and the biggest problems that can be encountered while performing AIO (all-in-one) installation are with Swift.

In order to perform AIO installation for Swift the following instructions must be followed:


With some modifications according to normal installation instructions of Juno on Ubuntu (just use common sense to modify e.g. IPs accordingly, add keystone authentication as it is missing in AIO). After this installation command swift stat works properly.

If any swift related process does not start then it needs to be ensured that e.g. log directories/files have owner set to swift:swift.