-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 1.6.0
-
Fix Version/s: 1.6.0
-
Component/s: None
-
Labels:None
-
Story Points:3
Bgpls functionality test fails to POST
{
"apps": {
"org.onosproject.provider.bgp.cfg": {
"bgpapp": {
"bgpPeer": [
{
"peerIp": "10.128.8.10",
"peerHoldTime": 120,
"remoteAs": 100,
"connectMode": "active"
}
],
"maxSession": 20,
"localAs": 100,
"flowSpecCapability": "IPV4",
"routerId": "10.128.8.11",
"lsCapability": true,
"largeAsCapability": false,
"holdTime": 180,
"flowSpecRpdCapability": false
}
}
}
}
to /network/configuration.
On master before switching to 1.7.0-SNAPSHOT(1.6 branch created) this results in a 200. On 1.6.0-rc1 it also return a 200. It also works on master HEAD with 200.
Commits between 1.6.0-rc2 and 1.6.0-rc3 this POST returns a 404 response code or 507 or 503.
On 1.6.0-rc4 this POST returns a 207 with an empty body. But POSTing the configuration to the most specific url gives a 200.
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 10157,2 | Fix for ONOS-4740 | onos-1.6 | onos | Status: MERGED | +2 | +1 |
| 10164,1 | Fix for ONOS-4740 | master | onos | Status: MERGED | +2 | +1 |