external routes can't be specified with empty gateway
Bug #1452155 reported by
Ivar Lazzaro
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy Client |
Fix Released
|
High
|
Sumit Naiksatam | ||
Bug Description
For external segments, today external routes can be specified as follows:
gbp external-
However, the GBP server supports an empty next hop which indicates the intent of using the default gateway for that specific external segment. This can't be specified trough the CLI. Using this:
gbp external-
Will send an empty string to the GBP server, while the following:
gbp external-
Will send the string 'None'.
The server is expecting None (as null, not as a string even if empty) to indicate the empty nexthop.
| Changed in group-based-policy-client: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| milestone: | none → next |
Revision history for this message
| Sumit Naiksatam (snaiksat) wrote | #1 |
| Changed in group-based-policy-client: | |
| assignee: | nobody → Sumit Naiksatam (snaiksat) |
| status: | Confirmed → Fix Committed |
| milestone: | next → 1.0.0 |
| Changed in group-based-policy-client: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This was fixed by: https:/