On start services incorrectly set RPC client and serializer version pinning
Bug #1569299 reported by
Gorka Eguileor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Gorka Eguileor |
Bug Description
When a service starts (c-sch, c-bak, c-vol) they set the versions for the RPC client and serializer using existing Service entries in the DB, but they don't consider themselves when determining the minimum version.
By not considering themselves we have 2 problematic scenarios:
1- When a service is first started it will pin to None version since there are no Services in the DB
2- When a service is upgraded and restarted it will pin to the old version since the entry in the DB has not been updated yet.
Changed in cinder: | |
assignee: | nobody → Gorka Eguileor (gorka) |
Changed in cinder: | |
importance: | Undecided → Medium |
tags: | added: mitaka-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/304685
Review: https:/