Skip soft-deleted records in 330_enforce_mitaka_online_migrations
The 330_enforce_mitaka_online_migrations migration considers
soft-deleted records as unmigrated (the blocker migration uses the
select function from sqlalchemy), but the online migrations only
migrate non-deleted records (the migrations use the model_query
function which defaults to read_deleted='no'). So even after running
all of the online migrations, operators can get stuck until they can
hard delete any soft-deleted compute_nodes, aggregates, and
pci_devices records they have.
Reviewed: https:/ /review. openstack. org/435546 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=6d64b727441 0ae45b95bd7ac7f 702c16daaa0fcd
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6d64b7274410ae4 5b95bd7ac7f702c 16daaa0fcd
Author: melanie witt <email address hidden>
Date: Fri Feb 17 17:27:57 2017 +0000
Skip soft-deleted records in 330_enforce_ mitaka_ online_ migrations
The 330_enforce_ mitaka_ online_ migrations migration considers
soft-deleted records as unmigrated (the blocker migration uses the
select function from sqlalchemy), but the online migrations only
migrate non-deleted records (the migrations use the model_query
function which defaults to read_deleted='no'). So even after running
all of the online migrations, operators can get stuck until they can
hard delete any soft-deleted compute_nodes, aggregates, and
pci_devices records they have.
Closes-Bug: #1665719
Change-Id: I2285005098b7da b7753366f53667f f8d4532d668