yahoo-eng-team team mailing list archive

[Balazs Gibizer <1978549@xxxxxxxxxxxxxxxxxx>]

I documented that can_host can be manually removed from the DB in
https://review.opendev.org/c/openstack/placement/+/845730 I set this bug
to Won't Fix as I don't think we want to go back to stein and add a DB
migration or change the initial DB schema of Placement. Feel free to set
it back to New if you disagree

** Changed in: nova
       Status: New => Won't Fix

** Tags added: db placement

-- 
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):
  Won't Fix

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