Slave provisioning procedure failing when trying to create slave with different datastore and version
Bug #1357709 reported by
Denis M.
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
In Progress
|
Medium
|
Yao Wang | ||
Bug Description
Since slave is being provisioned by POST against /instances/ (create call of instance/models.py) 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 https:/
| description: | updated |
| Changed in trove: | |
| assignee: | nobody → Denis M. (dmakogon) |
| milestone: | none → juno-3 |
| Changed in trove: | |
| importance: | Undecided → Medium |
Revision history for this message
| Greg Lucas (glucas-q) wrote | #1 |
| Changed in trove: | |
| status: | New → Triaged |
| Changed in trove: | |
| milestone: | juno-3 → ongoing |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to trove (master) | #2 |
| 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) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on trove (master) | #3 |
Revision history for this message
| Luigi Toscano (ltoscano) wrote | #4 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Related fix proposed to trove (master) | #5 |
| Changed in trove: | |
| status: | In Progress → Confirmed |
| assignee: | Denis M. (dmakogon) → nobody |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to trove (master) | #6 |
| Changed in trove: | |
| assignee: | nobody → Yao Wang (nihaome521) |
| status: | Confirmed → In Progress |
To post a comment you must log in.
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.