Upgrade murano with adding murano-node causes service fault
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fuel-plugin-murano |
Fix Released
|
High
|
Denis Egorenko |
Bug Description
Scenario:
1. Revert shapshot with box murano installation
2. Upload plugin to master node
3. Install plugin
4. Activate plugin and add new node
with murano-node role to the cluster
5. Update cluster (Deploy changes)
6. Run OSTF
Murano OSTF failed.
Traceback:
<131>Sep 21 20:18:02 node-2 murano-engine: 2016-09-21 20:18:02.607 22523 ERROR murano.
during invocation of <load>
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
2016-09-21 20:18:02.607 22523 ERROR murano.
Info:
It looks that old service wasn't stopped/updated and request comes to old service. So, since the DB is common, the Core library have 1.4 MPL version which ws not supported by the mitaka Murano which causes server fault.
Changed in fuel-plugin-murano: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → 1.0.0 |
Changed in fuel-plugin-murano: | |
milestone: | 1.0.0 → 1.0.1 |
Changed in fuel-plugin-murano: | |
assignee: | nobody → Denis Egorenko (degorenko) |
Changed in fuel-plugin-murano: | |
status: | In Progress → Fix Committed |
Changed in fuel-plugin-murano: | |
status: | Fix Committed → Fix Released |
https:/ /review. openstack. org/377368