miss doing aging when ovsdb reconnect to df
Bug #1630482 reported by
hujie
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DragonFlow |
Fix Released
|
Undecided
|
hujie | ||
Bug Description
when a new started df controller establish the connection to ovsdb, if there is no canary flow in the flow table, the aging will set the self.do_aging to False and add the canary flow by the init cookie value, when ovsdb reconnect to df controller, if df controller find the canary flow exis, it will renew the cookie value and send flows by new cookie, however the value of self.do_aging is False, so df controller will not do the aging.
| Changed in dragonflow: | |
| assignee: | nobody → hujie (mike-hu) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to dragonflow (master) | #1 |
| Changed in dragonflow: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to dragonflow (master) | #2 |
| Changed in dragonflow: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/