Fuel for OpenStack

  1. Bug #1396163
  2. Comment #3

Comment 3 for bug 1396163

Revision history for this message
Andrey Danin (gcon-monolake) wrote : Re: Fuel 5.1.1 + NSX. Instances do not receive the network configuration

Here is a workaround:

Remove Corosync resource bindings (collocations and orders) tied up with clone_p_neutron-openvswitch-agent:
crm configure delete dhcp-after-ovs
crm configure delete dhcp-with-ovs
crm configure delete l3-after-ovs
crm configure delete l3-with-ovs

Then run 'crm configure’ command and add a location for neutron-l3-agent for all controllers. The exact names of the controllers you can find by running "crm configure show|grep 'location p_neutron-dhcp-agent’” command.

Here is an example:
[root@node-1 ~]# crm configure delete dhcp-after-ovs
[root@node-1 ~]# crm configure delete dhcp-with-ovs
[root@node-1 ~]# crm configure delete l3-after-ovs
[root@node-1 ~]# crm configure delete l3-with-ovs
[root@node-1 ~]# crm configure show|grep 'location p_neutron-dhcp-agent'
location p_neutron-dhcp-agent_on_node-1.test.domain.local p_neutron-dhcp-agent 0: node-1.test.domain.local
location p_neutron-dhcp-agent_on_node-2.test.domain.local p_neutron-dhcp-agent 0: node-2.test.domain.local
location p_neutron-dhcp-agent_on_node-3.test.domain.local p_neutron-dhcp-agent 0: node-3.test.domain.local
[root@node-1 mirantis]# crm configure
crm(live)configure# location p_neutron-l3-agent_on_node-1.test.domain.local p_neutron-l3-agent 0: node-1.test.domain.local
crm(live)configure# location p_neutron-l3-agent_on_node-2.test.domain.local p_neutron-l3-agent 0: node-2.test.domain.local
crm(live)configure# location p_neutron-l3-agent_on_node-3.test.domain.local p_neutron-l3-agent 0: node-3.test.domain.local