Legacy MySQL datastore is shown on datastore-list
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
Edmond Kotowski |
Bug Description
Legacy MySQL is shown when calling trove datastore-list. Creating an instance with this datastore will cause the create call to fail. Some ideas for a fix would be to mark the database as active=False or upgrade the datastore list call to not return back the "Legacy MySQL" datastore.
+------
| ID | Name |
+------
| 10000000-
| 52abfff2-
| 7e422d1a-
| b58869c9-
+------
Changed in trove: | |
importance: | Undecided → Medium |
status: | New → Triaged |
milestone: | none → kilo-1 |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | kilo-1 → 2015.1.0 |
isn't this the artifact of some test that setup a datastore and didn't delete it, or that this came out of "redstack kick-start mysql"?