control-node sends malformed update when 26 or more networks are attached to SNAT instance
Bug #1454431 reported by
Pedro Marques
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R1.1 |
Fix Committed
|
High
|
Prakash Bailkeri | |||
R2.0 |
Fix Committed
|
High
|
Prakash Bailkeri | |||
R2.1 |
Fix Committed
|
High
|
Prakash Bailkeri | |||
R2.20 |
Fix Committed
|
High
|
Prakash Bailkeri | |||
Trunk |
Fix Committed
|
High
|
Prakash Bailkeri | |||
OpenContrail |
Fix Released
|
High
|
Pedro Marques |
Bug Description
Control-node doesn't know how to encode more than 31 Extended Communities in a BGP UPDATE message.
When a source-nat instance is attached to 20+ internal networks, the resulting numbers of extended communities ends up being more than 31 and the UPDATE is malformed.
The control-node also crashes when sending a Notification for an update that is more than 256 bytes.
Changed in opencontrail: | |
assignee: | nobody → Pedro Marques (5-roque) |
status: | New → Confirmed |
tags: | added: contrail-control |
Changed in opencontrail: | |
importance: | Undecided → High |
Changed in opencontrail: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/10270
Submitter: Pedro Marques (<email address hidden>)