Incorrect replication status on clusters
Bug #1758024 reported by
Gorka Eguileor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Gorka Eguileor |
Bug Description
When running a replicated service in a cluster, the replication_status field in the Cluster DB table doesn't get updated in some cases, making the cluster look like it's non replicated:
- When starting a new clustered replicated service cluster.
- When enabling replication on an already clustered service.
The reason for that is that the service and cluster creation happens on the Service's __init__ method, while the replication status isn't known until later, when the start method in the service calls the manager's init_host_with_rpc, where the manager updates the service DB entry.
Changed in cinder: | |
assignee: | nobody → Gorka Eguileor (gorka) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/555253
Review: https:/