Auston: We do think this a bug right? When we deploy through devstack with trove we shouldn't have a Legacy MySql datastore listed that we are unable to create an instance with. Do we think the fix would be to set the Legacy MySQL datastore to active=0 through a migration script?
Auston: We do think this a bug right? When we deploy through devstack with trove we shouldn't have a Legacy MySql datastore listed that we are unable to create an instance with. Do we think the fix would be to set the Legacy MySQL datastore to active=0 through a migration script?