Created attachment 947241 [details] log Description of problem: I am not sure yet whether it is a "feature" of some new rhel 7 kernel, but now it is not possible to add loopback to the bridge. # brctl addif br100 lo can't add lo to bridge br100: Invalid argument packstack is configuring in nova.conf flat_device=lo which means nova will try to add it to the brige, it fails horribly, VMs will end-up in ERROR and even deletion of them seems to be impossible. Version-Release number of selected component (if applicable): openstack-nova-compute-2014.1.3-2.el7ost.noarch openstack-packstack-2014.1.1-0.41.dev1251.el7ost.noarch kernel-3.10.0-123.8.1.el7.x86_64 How reproducible: easily, often (: Steps to Reproduce: 1. deploy 2. nova boot 3. fail Actual results: 2014-10-15 10:54:19.312 32629 TRACE nova.openstack.common.threadgroup NovaException: Failed to add interface: can't add lo to bridge br100: Invalid argument Expected results: VM active Additional info: This is a regression but likely it is not caused by packstack and I think we can workaround it in a while in our automation, so setting the Regression, but not a blocker.
I forgot to mention that we can workaround that by creating a dummy interface ip l add dummy0 type dummy which can be added to a bridge without an issue: brctl addif br100 dummy0 brctl show bridge name bridge id STP enabled interfaces br100 8000.6aebaa0f3eec no dummy0
This is probably just a TestBlocker, not a regression, as we seem to be deliberately setting 'CONFIG_NOVA_COMPUTE_PRIVIF': 'lo', 'CONFIG_NOVA_NETWORK_PRIVIF': 'lo', So it probably is not a failure of packstack. Although it is worthy to check what is the packstack's default.
Not a test blocker any more. The following was enough to workaround: set -e cat > /etc/sysconfig/network-scripts/ifcfg-dummy0 <<EOF DEVICE=dummy0 BOOTPROTO=none ONBOOT=yes TYPE=Ethernet NM_CONTROLLED=no EOF echo "alias dummy0 dummy" > /etc/modprobe.d/dummy.conf ifup dummy0
Related bug 1153128 ?
I have tested for this problem and it does not appear anymore