After failover Neutron port stays in binding_failed state
Bug #1483641 reported by
Ilya Shakhat
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
Critical
|
Eugene Nikanorov | ||
7.0.x |
Fix Released
|
Critical
|
Ilya Shakhat |
Bug Description
Traffic flow did not recover after cluster failover. The issue affects a single Neutron port. The user-visible impact depends on how the port was used. In the current case the affected port belongs to router, so the instance is still able to get IP address from DHCP, but has no access to gateway. In the OVS output the port has tag 4095 (DEAD_VLAN_TAG).
Steps to reproduce:
1. Deploy cluster with 3 controllers
2. Create several (3-4) networks and routers to increase the chances of failure
3. Spawn instances in every network
4. Suspend primary controller
5. Look for OVS ports with tag 4095
Changed in mos: | |
status: | New → Triaged |
Changed in mos: | |
assignee: | MOS Neutron (mos-neutron) → Ilya Shakhat (shakhat) |
Changed in mos: | |
status: | Triaged → In Progress |
tags: | added: on-verification |
tags: | removed: on-verification |
tags: | added: swarm-blocker |
no longer affects: | mos/8.0.x |
To post a comment you must log in.
VERSION: version: "2015.1.0-7.0" 07_10-37- 51" 8de55a0ac2557b6 0063a7961c5" fuelclient_ sha: "2b3d634df7ef11 9191e2d219c0030 60f599ad198" 9304cd04322ba0f b3dc9d30327" nailgun- agent_sha: "1512b9af6b41cc 95c4d891c593aee be0faca5a63" 40cbfb1a3acf80b 4176d15a2dc" 6848d44f2ff6198 87bca1b8427" 47f2491c865e029 e0ffea91c47" 519c7eddd8a840e e6ecba7f992"
feature_groups:
- mirantis
production: "docker"
release: "7.0"
openstack_
api: "1.0"
build_number: "874"
build_id: "2015-08-
nailgun_sha: "b508953557fc24
python-
fuel-agent_sha: "57145b1d880438
fuel-
astute_sha: "e1d3a435e5df5b
fuel-library_sha: "96781c2bf9584a
fuel-ostf_sha: "c7f745431aa3c1
fuelmain_sha: "bdca75d0256338