Slave provisioning procedure failing when trying to create slave with different datastore and version

Bug #1357709 reported by Denis M. on 2014-08-16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Yao Wang

Bug Description

Since slave is being provisioned by POST against /instances/ (create call of instance/ Trove should validate that slave datastore and version matching master's datastore and version.

Use case: master mysql-5.5, slave mongodb-2.0.9

Bug described at,cm

Denis M. (dmakogon) on 2014-08-16
description: updated
Changed in trove:
assignee: nobody → Denis M. (dmakogon)
milestone: none → juno-3
Denis M. (dmakogon) on 2014-08-18
Changed in trove:
importance: Undecided → Medium
Greg Lucas (glucas-q) wrote :

Capturing discussion for future reference:

There are scenarios where having a different datastore or version will work fine and it may be overly restrictive to prevent this.

Since backup/restore already performs this validation, we'd like to keep replication consistent. At some point we should revisit this restriction for both backup/restore and replication and consider whether there should be an option to allow mismatches or a way to configure valid combinations.

Changed in trove:
status: New → Triaged
Changed in trove:
milestone: juno-3 → ongoing

Fix proposed to branch: master

Changed in trove:
status: Triaged → In Progress
Changed in trove:
assignee: Denis M. (dmakogon) → Riddhi (ridhi-j-shah)
Changed in trove:
assignee: Riddhi (ridhi-j-shah) → Denis M. (dmakogon)

Change abandoned by Denis M. (<email address hidden>) on branch: master

Luigi Toscano (ltoscano) wrote :

I guess the status should change, given that the patch was (unfortunately) abandoned.

Related/more general bug:

Amrith Kumar (amrith) on 2016-04-05
Changed in trove:
status: In Progress → Confirmed
assignee: Denis M. (dmakogon) → nobody

Fix proposed to branch: master

Changed in trove:
assignee: nobody → Yao Wang (nihaome521)
status: Confirmed → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers