Max_Flows_Provisioning: After removing VMI level configuration , it is not considering value from VN level
Bug #1806866 reported by
Mohanperiyasamy M
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Committed
|
High
|
Kumar Harsh |
Bug Description
Precedence order between VMI level and VN level is not working properly.
>> After removing max_flows configuration ( by setting value as 0 or by attached newly created properties object ) @ VMI level, it is not taking value from VN level.
>> it is allowing all flows ( without any limit)
tags: | added: blocker |
information type: | Proprietary → Public |
To post a comment you must log in.
Precedence oder :
max_flows vmi > max_flows vn > max_flows set in agent.conf
setting max_flows=0 on vmi results to default value all flows are allowed .