robertstarmer
commented
10 years ago Most of us are headed to HK, so it may be a few days before we can investigate. Unless you find the glitch first. But the grizzly branch is intended to install from the older grizzly repositories, so it would seem at a minimum that there's a bit of version mismatch or more likely incorrect pinning occurring.
R
On Nov 3, 2013, at 3:14 AM, Loic Dachary notifications@github.com<mailto:notifications@github.com> wrote:
I setup a node to use the class group compute + controller. I setup another node to use the class group compute, both from a virgin 12.04.3 ubuntu. Using the openstack-installer stable/grizzly ( which ends up installing havana ). The compute + controller node has openvswitch 1.10 + openvswitchdatapath-dkms 1.10. The compute node has openvswitch 1.4 + openvswitchdatapath-dkms 1.4.
This creates complications as it seems 1.4 and 1.10 are subtly incompatible. The visible side effect was that gre tunels could not communicate when in_key=flow and out_key=flow, therefore VMs were unable to acquire their DHCP address.
— Reply to this email directly or view it on GitHubhttps://github.com/CiscoSystems/openstack-installer/issues/213.
ghost
I setup a node to use the class group compute + controller. I setup another node to use the class group compute, both from a virgin 12.04.3 ubuntu. Using the openstack-installer stable/grizzly ( which ends up installing havana ). The compute + controller node has openvswitch 1.10 + openvswitchdatapath-dkms 1.10. The compute node has openvswitch 1.4 + openvswitchdatapath-dkms 1.4.
This creates complications as it seems 1.4 and 1.10 are subtly incompatible. The visible side effect was that gre tunels could not communicate when in_key=flow and out_key=flow, therefore VMs were unable to acquire their DHCP address.