yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #89104
[Bug 1978549] [NEW] Placement resource_providers table has dangling column "can_host"
Public bug reported:
With bug https://bugs.launchpad.net/nova/+bug/1648197 or rather change
https://review.opendev.org/c/openstack/nova/+/461494 the can_host column
was removed from the resource_provider table in the placement db.
1) Apparently there is no migration task to also drop this column should
it exist already (due to an installation being older than this change),
see
https://opendev.org/openstack/placement/src/branch/master/placement/db/sqlalchemy/alembic/versions
See my comment https://bugs.launchpad.net/nova/+bug/1648197/comments/9
on how I ran into this while changing from PostgreSQL -> MariaDB on an
Ussuri installation.
2) I just might be confused here ... but it seems the column is still
used in Nova?
https://github.com/openstack/nova/blob/master/nova/db/main/migrations/versions/8f2f1571d55b_initial_version.py
** Affects: nova
Importance: Undecided
Status: New
--
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/1978549
Title:
Placement resource_providers table has dangling column "can_host"
Status in OpenStack Compute (nova):
New
Bug description:
With bug https://bugs.launchpad.net/nova/+bug/1648197 or rather change
https://review.opendev.org/c/openstack/nova/+/461494 the can_host
column was removed from the resource_provider table in the placement
db.
1) Apparently there is no migration task to also drop this column
should it exist already (due to an installation being older than this
change), see
https://opendev.org/openstack/placement/src/branch/master/placement/db/sqlalchemy/alembic/versions
See my comment https://bugs.launchpad.net/nova/+bug/1648197/comments/9
on how I ran into this while changing from PostgreSQL -> MariaDB on an
Ussuri installation.
2) I just might be confused here ... but it seems the column is still
used in Nova?
https://github.com/openstack/nova/blob/master/nova/db/main/migrations/versions/8f2f1571d55b_initial_version.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1978549/+subscriptions
Follow ups