L2 agent do not clear old QoS rules after restart
Bug #1812576 reported by
Chengqian Liu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Chengqian Liu |
Bug Description
This fix is optimized for https:/
BUG 1810025 only considers the case where the rule is emptied when the agent is stopped, and does not consider the case where the rule is deleted but not emptied when the agent is stopped.
Think about that:
1. Create two different types of rules, such as bandwidth_limit and minimum_bandwidth
2. Stop l2_agent
3. Delete a type of rule, such as bandwidth_limit
4. Start agent
5. Bandwidth_limit still exists
Changed in neutron: | |
assignee: | nobody → Chengqian Liu (liuchengqian90) |
Changed in neutron: | |
importance: | Undecided → Medium |
summary: |
- L2 agent do not clear old QoS rules after restart Edit + L2 agent do not clear old QoS rules after restart |
tags: | added: qos |
tags: | added: pike-backport-potential queens-backport-potential rocky-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/632014
Review: https:/