Red Hat Bugzilla – Bug 961567
floating ip association fails when nova-network does not have access to ebtables
Last modified: 2016-01-04 09:41:47 EST
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum install -y http://rdo.fedorapeople.org/openstack/openstack-grizzly/rdo-release-grizzly-3.noarch.rpm
2. yum install -y openstack-packstack
3. packstack --install-hosts=controller,compute
4. launch an instance, try to associate a floating ip
The dashboard flashes success with a public IP. nova-manage floating list reports a public IP taken. nova list and dashboard do not show associated public IP with the instance. The nat iptables shows entries for the public IP routed to the instance's private IP. The public IP is not accessible on the public network. It is accessible on the controller host (running network and not compute).
nova list and dashboard show the associated IP. IP accessible on the public network.
The install-hosts option installs nova-network on the controller and nova-compute on the compute nodes. nova-compute has a dependency on ebtables. nova-network does not. nova-network silently (!!) fails when it cannot access ebtables.
Workaround is to manually install ebtables on the controller host.
Well found. ebtables is pulled in by libvirt.
So I'll add the dependency on ebtables in the openstack-nova-network
subpackage in the appropriate places.
Seems this is a new grizzly dependency.
Fixed committed at:
Package updated in RDO repo