"nova-manage db online_data_migrations" doesn't report matched/migrated properly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
When running "nova-manage db online_
However, most of the migration routines are not properly reporting the "total matched" count when "max_count" is specified. This makes it difficult to know whether you have to call it again or not when specifying "--max-count" explicitly.
Take for example Flavor.
main_db_ids = _get_main_
count_all = len(main_db_ids)
<snip>
return count_all, count_hit
If someone sees that there were 50 items total and 50 items were converted, they may think that all the work is done. It would be better to call _get_main_
Alternately, we should document that if --max-count is used then "nova-manage db online_
description: | updated |
tags: | added: nova-manage |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |