yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxx>]

According to [1], the "deleted" column is an Integer since at least
the Havanna release. It looks like you missed to do the database
migrations for each release. Please be aware the release upgrades
must be done one after the other. Omitting one release is not supported.
Based on this, this bug report is "invalid" IMO.

If you have questions to this, please contact me in IRC in the channel
#openstack-nova, my name there is "markus_z".

References:
[1] https://git.openstack.org/cgit/openstack/nova/tree/nova/db/sqlalchemy/migrate_repo/versions/160_havana.py?id=36388f0510140ab4e2ffd63d7feff901a9cc4e58#n788

** Changed in: nova
       Status: Confirmed => Invalid

** Changed in: nova
     Assignee: Anseela M M (anseela-m00) => (unassigned)

-- 
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/1566025

Title:
  Unable to delete security groups; security_group table 'deleted' field
  needs migration

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  My long-standing Nova installation has the following columns in the
  security_groups table:

   +-------------+--------------+------+-----+---------+----------------+
   | Field       | Type         | Null | Key | Default | Extra          |
   +-------------+--------------+------+-----+---------+----------------+
   | created_at  | datetime     | YES  |     | NULL    |                |
   | updated_at  | datetime     | YES  |     | NULL    |                |
   | deleted_at  | datetime     | YES  |     | NULL    |                |
   | deleted     | tinyint(1)   | YES  | MUL | NULL    |                |
   | id          | int(11)      | NO   | PRI | NULL    | auto_increment |
   | name        | varchar(255) | YES  |     | NULL    |                |
   | description | varchar(255) | YES  |     | NULL    |                |
   | user_id     | varchar(255) | YES  |     | NULL    |                |
   | project_id  | varchar(255) | YES  |     | NULL    |                |
   +-------------+--------------+------+-----+---------+----------------+

  A more recent install looks like this:

   +-------------+--------------+------+-----+---------+----------------+
   | Field       | Type         | Null | Key | Default | Extra          |
   +-------------+--------------+------+-----+---------+----------------+
   | created_at  | datetime     | YES  |     | NULL    |                |
   | updated_at  | datetime     | YES  |     | NULL    |                |
   | deleted_at  | datetime     | YES  |     | NULL    |                |
   | id          | int(11)      | NO   | PRI | NULL    | auto_increment |
   | name        | varchar(255) | YES  |     | NULL    |                |
   | description | varchar(255) | YES  |     | NULL    |                |
   | user_id     | varchar(255) | YES  |     | NULL    |                |
   | project_id  | varchar(255) | YES  | MUL | NULL    |                |
   | deleted     | int(11)      | YES  |     | NULL    |                |
   +-------------+--------------+------+-----+---------+----------------+

  Note that the 'deleted' field has changed types.  It now stores a
  group ID upon deletion.  But, the old table can't store that group ID
  because of the tinyint data type.  This means that security groups
  cannot be deleted.

  I haven't yet located the source of this regression, but presumably it
  happened when the table definition was changed to use
  models.SoftDeleteMixin, and the accompanying migration change was
  overlooked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1566025/+subscriptions