This problem occurs rarely, maybe 5% of deployments. Probably only when one is deploying a compute node on separate servers.
The problem was in case you had separate compute nodes in your setup. The race condition for firewall wasn't appended to manifestfor them. So I suggest running setup with 1 controller node and 1+ compute nodes. You can also check in /var/tmp/packstack/<YYMMDD-hhmmss>-<random>/manifests/<compute_host_ip>_nova.pp.log that firewall rule '001 nova compute incoming' is applied before class 'nova::compute::libvirt' (or more precisely before service 'libvirt').
(In reply to Martin Magr from comment #5) > The problem was in case you had separate compute nodes in your setup. The > race condition for firewall wasn't appended to manifestfor them. > > So I suggest running setup with 1 controller node and 1+ compute nodes. You > can also check in > /var/tmp/packstack/<YYMMDD-hhmmss>-<random>/manifests/<compute_host_ip>_nova. > pp.log that firewall rule '001 nova compute incoming' is applied before > class 'nova::compute::libvirt' (or more precisely before service 'libvirt'). Thank you!
Verified NVR: openstack-packstack-2013.1.1-0.8.dev601.el6ost.noarch Installed Openstack via packstack with 1 controller and 2 compute nodes. No errors were indicated in stdout nor in packstack logs.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0938.html