BGPaas port range modification requires config node to be restarted
Bug #1792335 reported by
richard roberts
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| Trunk |
Fix Committed
|
Medium
|
Yijie Xiao | |||
Bug Description
When changing the default port range of bgpaas (50000 - 50512), a restart of config node is required in order for this modification to be taken into account.
Although this is an operation that is not done on a regular basis, restarting a config node is still an invasive operation.
This LP is created to request that modification of bgpaas port range can be done "on the fly" without restarting the config node (which actually manages this port range).
| Changed in juniperopenstack: | |
| importance: | Undecided → Medium |
| milestone: | none → r5.1.1 |
| milestone: | r5.1.1 → r5.0.3 |
| milestone: | r5.0.3 → r5.1.1 |
| Changed in juniperopenstack: | |
| assignee: | nobody → Shivayogi Ugaji (shivayogi123) |
| tags: | added: config contrail-networking |
Revision history for this message
| Yijie Xiao (yixiao2018) wrote | #1 |
To post a comment you must log in.
From my perspective, this is the same issue as what I was working on: https:/