openstack
/
placement
Code Issues Proposed changes

Add WA about resource_providers.can_host removal 

We made a mistake and not added resource_providers.can_host to the new
DB schema of Placement when Placement was split out of Nova. This patch
documents that as can_host is not in the DB model it is safe to drop it
from the DB to remove the schema inconsistency.

Related-Bug: #1978549
Change-Id: Icfe83313e86969b0b9d34c19b6b82a47d685d4d7
This commit is contained in:
Balazs Gibizer 2022-06-14 13:31:18 +02:00
parent 5acaa2eec7
commit d8241aac9c
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/admin/upgrade-to-stein.rst
View File

@ -185,6 +185,17 @@ Migrate the Data
$ placement-manage db sync
.. note::
As described in `bug 1978549`_ the ``can_host`` column of the
``resource_providers`` table was removed from the DB model but not from the
DB schema while Placement was still part of Nova. Then when Placement was
split out its DB schema was altered to not contain ``can_host`` any
more. This can create a situation when the actual DB schema and the schema
defined by the alembic code is different. As ``can_host`` is not used any
more it is safe to manually remove it from the DB to remove the schema
inconsistency.
Finalize the Upgrade
--------------------
@ -209,3 +220,4 @@ Finalize the Upgrade
.. _release notes: https://docs.openstack.org/releasenotes/placement/stein.html
.. _osc-placement: https://docs.openstack.org/osc-placement/latest/
.. _bug 2005478: https://storyboard.openstack.org/#!/story/2005478
.. _bug 1978549: https://bugs.launchpad.net/nova/+bug/1978549