yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #63101
[Bug 1681431] Re: "nova-manage db sync" fails from Mitaka to Newton because deleted compute nodes
*** This bug is a duplicate of bug 1665719 ***
https://bugs.launchpad.net/bugs/1665719
Already fixed #1665719
** Changed in: nova
Status: New => 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/1681431
Title:
"nova-manage db sync" fails from Mitaka to Newton because deleted
compute nodes
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===========
"nova-manage db sync" fails from Mitaka to Newton because deleted compute nodes
DB migration from Mitaka to Newton fails in migration 330 with:
"error: There are still XX unmigrated records in the compute_nodes table. Migration cannot continue until all records have been migrated."
This migration checks if there are compute_nodes without a UUID.
However, "nova-manage db online_data_migrations" in Mitaka only
migrates non deleted compute_node entries.
Steps to reproduce
==================
1) Have a nova Mitaka DB (319)
2) Make sure you have a deleted entry (deleted>0) in "compute_nodes" table.
3) Make sure all data migrations are done in Mitaka. ("nova-manage db online_data_migrations")
4) Sync the DB for Newton. ("nova-manage db sync" in a Newton node)
Expected result
===============
DB migrations succeed (334)
Actual result
=============
DB doesn't migrate (329)
Environment
===========
Tested with "13.1.2" and "14.0.3".
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1681431/+subscriptions
References