No default qos objects created on upgrade from 3.0 to 3.1
Bug #1605984 reported by
Vedamurthy Joshi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.1 |
Fix Committed
|
High
|
Naveen N | |||
Trunk |
Fix Committed
|
High
|
Naveen N |
Bug Description
R3.1 Build 4 (from 3.0.2 Build 50)
Upgraded from 3.0 to 3.1 Build 4
No qos objects are created after upgrade
root@nodei27:~# ./api-inspect.py fcs --debug
Command : curl -u admin:contrail123 -X GET http://
{
"forwarding
}
root@nodei27:~# ./api-inspect.py qos-configs --debug
Command : curl -u admin:contrail123 -X GET http://
{
"qos-configs": []
}
root@nodei27:~#
Default instances of these objects should not be needed. Will fix it by never generating default instances.