SM R3.0 2717 - SM status using tag throws irrelevant error message
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Won't Fix
|
Undecided
|
Unassigned | |||
Trunk |
Incomplete
|
Medium
|
sundarkh |
Bug Description
SM R3.0 2717 - SM status using tag throws irrelevant error message
root@nodeg19:
{
"cluster": [
{
"id": "clusterg37"
}
],
"image": [
{
"id": "buntu14juno2715"
},
{
"id": "ubuntu-12-04"
},
{
"id": "ubuntu-14-04"
},
{
"id": "ubuntu-14-04-1"
},
{
"id": "ubuntu14icehou
},
{
"id": "ubuntu14icehou
},
{
"id": "ubuntu14juno1"
},
{
"id": "ubuntu14juno124"
},
{
"id": "ubuntu14juno2715"
},
{
"id": "ubuntu14juno27
},
{
"id": "ubuntu14juno2717"
},
{
"id": "ubuntu14juno5"
},
{
"id": "ubuntu14kilo1"
},
{
"id": "ubuntu14kilo2713"
}
],
"server": [
{
"id": "nodeg37",
}
],
"tag": {
"tag1": "test0",
"tag2": "datacenter"
}
root@nodeg19:
{
"return_code": 9,
"return_data": null,
"return_msg": "IndexError('list index out of range',)" >>>>>>> Error message not helpful.
}
Marking it as invalid, As this is very very old bug.