Comment 9 for bug 1671354

I think, there is still an issue... When I create a volume, delete it, change the corresponding timestamps in the database and run "cinder-manage db purge" -> OK!

When I create a volume and attach it to a VM, detach it, remove it, change the corresponding timestamps in the database and run "cinder-manage db purge" -> Purge command failed, check cinder-manage logs for more details.

The table "volume_admin_metadata" contains an entry where "deleted" is set, but the column "deleted_at" is empty:

INSERT INTO `volume_admin_metadata` (`created_at`, `updated_at`, `deleted_at`, `deleted`, `id`, `volume_id`, `key`, `value`) VALUES ('2017-03-27 11:23:50', '2017-03-27 11:23:50', NULL, 1, 19, '6582f0e6-e703-4c39-bb01-769fb21a4c90', 'readonly', 'False');

I think the detach action does not add the "deleted_at" timestamp to the entry. It gets only marked as deleted. This causes "cinder-manage db purge" to fail.

That does not look right. What do you think?