Graceful OVS restart: not all flows get updated cookie

Bug #1480292 reported by Ann Taraday
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Released
Medium
Ann Taraday

Bug Description

Graceful OVS restart set flows cookie as agent_stamp_id, not all flow's cookie's get updated for br-tun https://paste.mirantis.net/show/833/

This does not effect connectivity of vms as all necessary flows are still available, just does not get right cookie. This problem appeared as some flows are created with mod-flow method, not add-flow.

Tags: neutron
Changed in mos:
status: New → In Progress
importance: Undecided → Low
Changed in mos:
milestone: none → 7.0
importance: Low → Medium
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix proposed to openstack/neutron (openstack-ci/fuel-7.0/2015.1.0)

Fix proposed to branch: openstack-ci/fuel-7.0/2015.1.0
Change author: Ann Kamyshnikova <email address hidden>
Review: https://review.fuel-infra.org/10034

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix merged to openstack/neutron (openstack-ci/fuel-7.0/2015.1.0)

Reviewed: https://review.fuel-infra.org/10034
Submitter: mos-infra-ci <>
Branch: openstack-ci/fuel-7.0/2015.1.0

Commit: e05c62e39a3f9c5dd173eb2315625ccc881ee55b
Author: Ann Kamyshnikova <email address hidden>
Date: Mon Aug 3 12:27:52 2015

Add agent_stamp_id for mod-flow and learned_flow

Graceful OVS restart set flows cookie as agent_stamp_id, not all
flow's cookies get updated for br-tun, as ome flows are created with
mod-flow method, not add-flow.

Change-Id: I8eee9bcbcedb8e33a10d19bfdbbfd7b8153c3e50
Closes-bug: #1480292

Changed in mos:
status: In Progress → Fix Committed
Anna Babich (ababich)
tags: added: on-verification
Revision history for this message
Anna Babich (ababich) wrote :

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "7.0"
  openstack_version: "2015.1.0-7.0"
  api: "1.0"
  build_number: "252"
  build_id: "2015-08-29_17-24-57"
  nailgun_sha: "3189ccfb8c1dac888e351f535b03bdbc9d392406"
  python-fuelclient_sha: "9643fa07f1290071511066804f962f62fe27b512"
  fuel-agent_sha: "1e8f38bbb864ed99aa8fe862b6367e82afec3263"
  fuel-nailgun-agent_sha: "d7027952870a35db8dc52f185bb1158cdd3d1ebd"
  astute_sha: "53c86cba593ddbac776ce5a3360240274c20738c"
  fuel-library_sha: "f05b958ef318f70170fe0db71bffcbaadbc39ae4"
  fuel-ostf_sha: "83048d68609854324ceeaf04242e68d658cfb55d"
  fuelmain_sha: "0e54d68392b359bc122e5bbba9249c729eeaf579"

Verified on cluster: neutron+vxlan, 3 controllers, 2 computes

Verification scenario
1. Create four networks and launch two instances per each network
2. Run the script against master node:
#!/bin/bash
# $1 - controller on what we should disable agents
#Disable/enable ovs-agents on controllers
ssh root@$1 '. openrc && pcs resource disable p_neutron-plugin-openvswitch-agent'
ssh root@$1 '. openrc && pcs resource enable p_neutron-plugin-openvswitch-agent'
#Restart ovs-agents on computes
for i in $(fuel node | grep compute | awk '{print$1}'); do ssh node-$i 'service neutron-plugin-openvswitch-agent restart'; done
# wait restart
sleep 30
3. On every node check that there are no flows with cookie=0х0:
ovs-ofctl dump-flows br-tun | grep cookie

tags: removed: on-verification
Changed in mos:
status: Fix Committed → Fix Released
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Fix proposed to openstack/neutron (openstack-ci/fuel-8.0/liberty)

Fix proposed to branch: openstack-ci/fuel-8.0/liberty
Change author: Ann Kamyshnikova <email address hidden>
Review: https://review.fuel-infra.org/13295

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Change abandoned on openstack/neutron (openstack-ci/fuel-8.0/liberty)

Change abandoned by Ann Kamyshnikova <email address hidden> on branch: openstack-ci/fuel-8.0/liberty
Review: https://review.fuel-infra.org/13295
Reason: his change was merged in upstream as part of https://review.openstack.org/#/c/182920/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.