Cannot associate floating ip to an instance on Centos deployment (HA GRE)

[Kirill Omelchenko]

Cluster config: (CentOS) 3x Controllers, 2x Computes, Neutro GRE networking.

[root@nailgun ~]# cat /etc/fuel/version.yaml
VERSION:
  mirantis: "yes"
  production: "docker"
  release: "5.0.1"
  api: "1.0"
  build_number: "163"
  build_id: "2014-08-04_00-31-14"
  astute_sha: "6db5f5031b74e67b92fcac1f7998eaa296d68025"
  fuellib_sha: "dec8421a18e3ccfa35978b36b5de3292b53e6b69"
  ostf_sha: "09b6bccf7d476771ac859bb3c76c9ebec9da9e1f"
  nailgun_sha: "04ada3cd7ef14f6741a05fd5d6690260f9198095"
  fuelmain_sha: "f78dd3a3b76058d8d1984167886be3f044554fcc"

Though all services seem to be running:

[root@node-2 log]# neutron agent-list
+--------------------------------------+--------------------+--------------------------+-------+----------------+
| id | agent_type | host | alive | admin_state_up |
+--------------------------------------+--------------------+--------------------------+-------+----------------+
| 1272f312-4148-423e-a212-c9edd71b659a | Open vSwitch agent | node-2.test.domain.local | :-) | True |
| 2f1bae9b-2d8e-4ee2-b59b-0aa7f6259dca | Open vSwitch agent | node-4.test.domain.local | :-) | True |
| 31825e70-3da2-4f00-a4e6-ef39d3080795 | Open vSwitch agent | node-1.test.domain.local | :-) | True |
| 3576608d-d170-48bc-963f-55bc3067ce9d | Open vSwitch agent | node-3.test.domain.local | :-) | True |
| 421b3d2e-1590-48c7-b131-a148575484e8 | L3 agent | node-1.test.domain.local | :-) | True |
| 5998572c-e41e-4c38-bdb1-3e7e2997ba45 | DHCP agent | node-2.test.domain.local | :-) | True |
| a22abac1-831b-4b9b-986c-4fae199ae82d | Metadata agent | node-1.test.domain.local | :-) | True |
| c5642684-e32d-4411-be0d-9f04433dfa1e | Metadata agent | node-2.test.domain.local | :-) | True |
| ccc0ced3-b125-4457-9460-5fb219a5adf6 | Metadata agent | node-5.test.domain.local | :-) | True |
| edf7e832-ada2-46ea-a0e4-5ce5e4e8aa24 | Open vSwitch agent | node-5.test.domain.local | :-) | True |
+--------------------------------------+--------------------+--------------------------+-------+----------------+

Tunels config:
http://paste.openstack.org/show/90051/

Nor OSTF passes the test of floating ip assosiation, niether works manualy with the help of OS UI. (See the attached screenshots.)

[Eugene Nikanorov (enikanorov)]

That seems to be an issue with router, it ether has not been created or has not been plugged to tenant subnet.
I'm analyzing logs at the moment.

[Eugene Nikanorov (enikanorov)]

Per first screenshot: error message says that external network X is not reachable from subnet Y, where Y is a subnet from network X (external network).

Apparently there's some issue in OSTF that is trying either to plug VM into external network and then associate floating IP to it, or some other issue.

Networking configuration seems to be correct.

[Eugene Nikanorov (enikanorov)]

I think we need to look at another repro before raising importance of this bug.

[Kirill Omelchenko (komelchenko)]

Eugene,

> Apparently there's some issue in OSTF that is trying either to plug VM into external network and then associate floating IP to it, or some other issue

I have reproduced the issue manually as can be seen from the screenshots.
Steps to reproduce:
1. Go to Horizon
2. Create a simple instance
3. Wait for instance status to become Active
4. Try to associate Floating IP

Expected: IP gets associated

Actual: UI pops up errors displayed on the screenshot attached above.

Which evidently points to the fact that OSTF is not the root of the problem.

[Eugene Nikanorov (enikanorov)]

OSTF failures could not be reproduced, floating ip connectivity seems to be ok.

The described issue was the result of VM being plugged into external network directly (which is not supported in Neutron).
So floating IP could not be associated with the port on external network.