It comes from the migration script 019_datastore_fix.py in the method create_legacy_version. This is why I thought the cleanest fix would be to add a migration scripts that sets the Active flag to false so it won't show up when you call datastore-list.
Here is the a snippet from the 019_datastore.py:
def create_legacy_version(datastores_table, datastore_versions_table, image_id):
insert( table=datastores_table, values=dict(id=LEGACY_DATASTORE_ID, name="Legacy MySQL")
).execute()
It comes from the migration script 019_datastore_ fix.py in the method create_ legacy_ version. This is why I thought the cleanest fix would be to add a migration scripts that sets the Active flag to false so it won't show up when you call datastore-list.
Here is the a snippet from the 019_datastore.py: legacy_ version( datastores_ table,
datastore_ versions_ table,
image_ id):
table= datastores_ table,
values= dict(id= LEGACY_ DATASTORE_ ID, name="Legacy MySQL")
def create_
insert(
).execute()
insert(
table= datastore_ versions_ table,
values= dict(id= LEGACY_ VERSION_ ID,
datastore _id=LEGACY_ DATASTORE_ ID,
name= "Unknown Legacy Version",
image_ id=image_ id,
packages= "",
active= False,
manager= "mysql" )
).execute()
return LEGACY_VERSION_ID