yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1846606@xxxxxxxxxxxxxxxxxx>]

** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1846606

Title:
  [mysql8] Unknown column 'public' in 'firewall_rules_v2'

Status in neutron:
  Fix Released
Status in neutron-fwaas package in Ubuntu:
  Fix Released

Bug description:
  I installed a fresh openstack test cluster in eoan today (October 3).

  Neutron database initialization with the command:
  sudo su -s /bin/sh -c "neutron-db-manage
    --config-file /etc/neutron/neutron.conf
    --config-file /etc/neutron/plugins/ml2/ml2_conf.ini
     upgrade head" neutron

  failed with error message:
  oslo_db.exception.DBError: (pymysql.err.InternalError) (1054, "Unknown column 'public' in 'firewall_rules_v2'") [SQL: 'ALTER TABLE firewall_rules_v2 CHANGE public shared BOOL NULL'] (Background on this error at: http://sqlalche.me/e/2j85)

  In mysql the table and the column exist, with a constraint on the column:
  CONSTRAINT `firewall_rules_v2_chk_1` CHECK ((`public` in (0,1))),

  manually updating the column in mysql failed with the same error message.
  mysql> ALTER TABLE firewall_rules_v2 CHANGE public shared BOOL NULL;
  ERROR 1054 (42S22): Unknown column 'public' in 'check constraint firewall_rules_v2_chk_1 expression'

  I guessed the constraint did not like it if the name of the column was changed.
  I removed the column 'private' and created it again, without the constraint. The the alter table command worked fine.
  After doing the same for the private columns in tables firewall_groups_v2 and firewall_policies_v2 Neutron could initialize the database and all was fine (I could create a network and start an instance).

  neutron 2:15.0.0~rc1-0ubuntu1
  mysql-server 8.0.16-0ubuntu3

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