** Changed in: nova
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1062474
Title:
Migrations do not populate volume_id_mappings and instance_id_mappings
completely
Status in OpenStack Compute (Nova):
Invalid
Bug description:
089_add_volume_id_mappings.py
107_add_instance_id_mappings.py
These two migrations create tables that easily map volume and
instance IDs to UUIDs. Each have 6 columns: id, uuid, created_at,
updated_at, deleted_at, deleted. Only the 'id' and 'uuid' column get
populated with data copied from the volumes or instances table in the
migration that creates them. From what I can tell, none of these
fields are currently being used by code anywhere in Folsom, but this
has already introduced a nasty Bug #1061166.
If the plan is to be able to query this info from this table in
Grizzly, they should be fully populated with data for existing
instances. If there is no plan to make use of them, they should be
dropped.
Additionally, there should probably be some uniqueness constraints on
those tables to ensure these mappings stay consistent if similar bugs
exist elsewhere in the code base.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1062474/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
