-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Duplicate
-
Affects Version/s: 1.12.0
-
Fix Version/s: 1.12.0
-
Component/s: None
-
Labels:
-
Environment:
three docker containers with newest onosproject/onos image.
-
Epic Link:
three docker containers with newest onosproject/onos image.
Steps to go to bad status :
0. At CLIs of three nodes, run log:tail
1. login Web Pages of three nodes, such as http://10.103.71.13:8181/onos/ui/
2. Post cluster configuration through Rest API /cluster/configuration, to just one of three nodes, e.g. node A.
And we can see, node A is restarting. After A restarted, error log will print at A and another two nodes.
Finally, the other two nodes will work badlly, for example, their web page will not work !!!
please pay attention: we do nothing at the other two nodes !!!
Post data for /cluster/configuration:
{
"nodes": [
{
"id": "172.17.0.2",
"ip": "172.17.0.2",
"tcpPort": 9876,
"status": "ACTIVE"
},
{
"id": "172.17.0.3",
"ip": "172.17.0.3",
"tcpPort": 9876,
"status": "ACTIVE"
},
{
"id": "172.17.0.4",
"ip": "172.17.0.4",
"tcpPort": 9876,
"status": "ACTIVE"
},
]
}