Schema transformer could crash after upgrading from 2.0 if there are any stale service chains
Bug #1535923 reported by
Sachin Bansal
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Sachin Bansal | |||
R2.21.x |
Fix Committed
|
High
|
Sachin Bansal | |||
R2.22.x |
Fix Committed
|
High
|
Sachin Bansal | |||
Trunk |
Fix Committed
|
High
|
Sachin Bansal |
Bug Description
Schema transformer could crash after upgrading from 2.0 if there are any stale service chains. This happens because a new member variable partially_created was added to ServiceChain class. We store service chain data in cassandra after pickling. After schema transformer comes up, we should check for this new variable before accessing it.
information type: | Proprietary → Public |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/16707
Submitter: Sachin Bansal (<email address hidden>)