[mos] External gateway seems down in horizon, but works

[Aviram Bar-Haim]

upstream bug: https://bugs.launchpad.net/neutron/+bug/1253634

ISO version: 4.1 custom iso with SRIOV support
Installation mode: 4.1 usual installation with OVS neutron plugin and ISER support in the cinder node

Ping and access to floating IP and from VM to 8.8.8.8 works fine but in horizon it seems that the router gateway is down.

When checking interfaces:
====
[root@node-1 ~]# ip netns exec qrouter-f802a42f-0b92-45ee-ae72-b3f8668298d5 ip l
19: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
20: qr-7d2687f9-0e: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether fa:16:3e:05:d2:27 brd ff:ff:ff:ff:ff:ff
21: qg-15c5198d-3d: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether fa:16:3e:c9:ed:c1 brd ff:ff:ff:ff:ff:ff
====

But via nova API:
====
[root@node-1 ~]# neutron port-show 15c5198d-3da1-44c0-b4cf-729658198d5f
+-----------------------+-------------------------------------------------------------------------------------+
| Field | Value |
+-----------------------+-------------------------------------------------------------------------------------+
| admin_state_up | True |
| allowed_address_pairs | |
| binding:capabilities | {"port_filter": true} |
| binding:host_id | node-1.domain.tld |
| binding:vif_type | ovs |
| device_id | f802a42f-0b92-45ee-ae72-b3f8668298d5 |
| device_owner | network:router_gateway |
| extra_dhcp_opts | |
| fixed_ips | {"subnet_id": "1d07221b-402a-4f8d-97cf-082642409af8", "ip_address": "10.209.37.59"} |
| id | 15c5198d-3da1-44c0-b4cf-729658198d5f |
| mac_address | fa:16:3e:c9:ed:c1 |
| name | |
| network_id | 8b5c53eb-c64b-4ea4-a05a-d4078eff6d0a |
| security_groups | |
| status | DOWN |
| tenant_id | |
+-----------------------+-------------------------------------------------------------------------------------+
====

[Andrey Epifanov (aepifanov)]

#release notes

On OpenStack installation with Neutron+OVS on the routers Port router_gateway is in status DOWN, but all works, instances can access the outside world and they also accessible from the outside by their floating IPs. It happens because Horizon and Neutron client take port status from the DB, but it's not updated by the agents.

[Andrey Epifanov (aepifanov)]

For the fix this issue we need to add default external_id flag for br-ex:
sudo ovs-vsctl br-set-external-id br-ex bridge-id br-ex

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/121898

[Eugene Nikanorov (enikanorov)]

Link to the upstream bug with an explanation:
https://bugs.launchpad.net/neutron/+bug/1253634

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/121898
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=e4a9fd00dfa6d2d2e189ab716e4736dc71c7801e
Submitter: Jenkins
Branch: master

commit e4a9fd00dfa6d2d2e189ab716e4736dc71c7801e
Author: Sergey Kolekonov <email address hidden>
Date: Tue Sep 16 19:02:08 2014 +0400

    Set non-empty external-id for bridges by default

    Set external-id for bridges to their names by default.
    OVS-agent monitors external bridges only if their external-id
    matches their names

    Change-Id: If98ff6d13d5d229127e5218c99d788b759e3027f
    Closes-bug: #1323608

[Anastasia Palkina (apalkina)]

Verified on ISO #33 for CentOS and Ubuntu

"build_id": "2014-10-21_00-01-06", "ostf_sha": "de177931b53fbe9655502b73d03910b8118e25f1", "build_number": "33", "auth_required": true, "api": "1.0", "nailgun_sha": "63dd9e6673142b56d290ac8dc3862093ad65745f", "production": "docker", "fuelmain_sha": "0e606011c99a302167061084c1637f9cdc85f017", "astute_sha": "6a11a7c481d116e6cfdb422fab1d4bbb29cbea1c", "feature_groups": ["mirantis"], "release": "6.0", "release_versions": {"2014.2-6.0": {"VERSION": {"build_id": "2014-10-21_00-01-06", "ostf_sha": "de177931b53fbe9655502b73d03910b8118e25f1", "build_number": "33", "api": "1.0", "nailgun_sha": "63dd9e6673142b56d290ac8dc3862093ad65745f", "production": "docker", "fuelmain_sha": "0e606011c99a302167061084c1637f9cdc85f017", "astute_sha": "6a11a7c481d116e6cfdb422fab1d4bbb29cbea1c", "feature_groups": ["mirantis"], "release": "6.0", "fuellib_sha": "d1beae25dc5f372656bf176bff68ed0ef3a45853"}}}, "fuellib_sha": "d1beae25dc5f372656bf176bff68ed0ef3a45853"

[Sergey Kolekonov (skolekonov)]

This bug isn't connected with MOS, because it's deployment issue.