Upgrade R2.02#64 to R2.21#103 - LBaaS VM name change doesn't take effect
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Rudra Rugge | |||
R2.20.x |
Fix Committed
|
High
|
Rudra Rugge | |||
R2.21.x |
Fix Committed
|
High
|
Rudra Rugge | |||
R3.0 |
Fix Committed
|
High
|
Rudra Rugge | |||
R3.1 |
Fix Committed
|
High
|
Rudra Rugge | |||
Trunk |
Fix Committed
|
High
|
Rudra Rugge |
Bug Description
After upgrade from R2.02#64 to R2.21#103, LBaaS VM name does not get changed to the latest scheme. Due to this, service monitor throws following traceback.
Traceback (most recent call last):
File "/usr/lib/
return route.call(**args)
File "/usr/lib/
rv = callback(*a, **ka)
File "/usr/lib/
return method(
File "/usr/lib/
handle_
File "/usr/lib/
if vm.index < len(si.
AttributeError: 'VirtualMachineSM' object has no attribute 'index'
Review in progress for https:/ /review. opencontrail. org/14835
Submitter: Rudra Rugge (<email address hidden>)