Fuel 5.1.1 + NSX + HA. Neutron L3 and DHCP agents do not start

[okosse]

HA deploy Fuel 5.1.1 environment with 5 CentOS nodes: 3 controller, compute and cinder. Instances do not receive the network configuration, as a consequence, the OSTF test "Check network connectivity from instance via floating IP" fails with error: "Instance is not reachable by IP. Please refer to OpenStack logs for more details. 5. Check connectivity to the floating IP using ping command."

This error does not occur when using simple mode CentOS.

---------------------fuel-version---------------------------------

api: '1.0'
astute_sha: dade74af41d4972fe05a1c16ae1db2a2e60c6715
auth_required: true
build_id: 2014-11-23_21-01-00
build_number: '34'
feature_groups:
- mirantis
fuellib_sha: 444339cae21c369c1d95e96c1059d4099077138e
fuelmain_sha: 0fe3db7475b9f8b287c5b59cba94c9a40a8d8101
nailgun_sha: 7580f6341a726c2019f880ae23ff3f1c581fd850
ostf_sha: 64cb59c681658a7a55cc2c09d079072a41beb346
production: docker
release: 5.1.1
release_versions:
  2014.1.3-5.1.1:
    VERSION:
      api: '1.0'
      astute_sha: dade74af41d4972fe05a1c16ae1db2a2e60c6715
      build_id: 2014-11-23_21-01-00
      build_number: '34'
      feature_groups:
      - mirantis
      fuellib_sha: 444339cae21c369c1d95e96c1059d4099077138e
      fuelmain_sha: 0fe3db7475b9f8b287c5b59cba94c9a40a8d8101
      nailgun_sha: 7580f6341a726c2019f880ae23ff3f1c581fd850
      ostf_sha: 64cb59c681658a7a55cc2c09d079072a41beb346
      production: docker
      release: 5.1.1

[Irina Povolotskaya (ipovolotskaya)]

I need workaround here for RN

[Andrey Danin (gcon-monolake)]

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

[Andrey Danin (gcon-monolake)]

We will document a workaround for 5.1.1. That's why I close this bug as "Won't Fix" for 5.1.1. Also the bug isn't affect 6.0 release, so closing it as "Invalid" for 6.0.

[Andrey Danin (gcon-monolake)]

Documented for 5.1.1 here https://review.openstack.org/#/c/130717