yahoo-eng-team team mailing list archive

[Cedric Brandily <1557785@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

auto_allocated_topology migration[1] adds the column nullable boolean column is_default to externalnetworks table. MySQL sets is_default to False during the migration (wtf?) where PostgreSQL sets is_default to NULL. It implies Neutron with PostgreSQL returns is_default == null for external-networks migrated from Liberty to Mitaka and is_default == 
False for non is_default external-networks created after Mitaka migration.


[1] neutron/db/migration/alembic_migrations/versions/mitaka/expand/19f26505c74f_auto_allocated_topology.py

** Affects: neutron
     Importance: Undecided
     Assignee: Cedric Brandily (cbrandily)
         Status: In Progress


** Tags: db l3-ipam-dhcp mitaka-rc-potential

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

Title:
  auto_allocated_topology migration generates inconsistent external
  networks with PostgreSQL

Status in neutron:
  In Progress

Bug description:
  auto_allocated_topology migration[1] adds the column nullable boolean column is_default to externalnetworks table. MySQL sets is_default to False during the migration (wtf?) where PostgreSQL sets is_default to NULL. It implies Neutron with PostgreSQL returns is_default == null for external-networks migrated from Liberty to Mitaka and is_default == 
  False for non is_default external-networks created after Mitaka migration.

  
  [1] neutron/db/migration/alembic_migrations/versions/mitaka/expand/19f26505c74f_auto_allocated_topology.py

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