yahoo-eng-team team mailing list archive

[Paul Michali <1336556@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I have a private repo that is a few weeks behind the upstream, and was
having problems stacking. Initially it was failing in one of the
migrations, so I changed the SQLAlchemy version to 0.8.4 and alembic to
0.6.5 and retried (clean database).

What I saw was that the migration worked, but later a router create
failed.  It was complaining that the enable_snat field was not specified
and did not have a default value. Checking in the migrations, I saw that
128e042a2b68_ext_gw_mode.py adds this field and sets the default value
to True. However, it was not doing that.

I changed the migration file to use server_default=sa.text("true") and
now the migration works. BTW, it was the only migration file using
'default=True'.

Not sure if we should just apply this change to the existing migration
file or if some other action is needed.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: migration

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

Title:
  migration default value not being applied to dbase

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  I have a private repo that is a few weeks behind the upstream, and was
  having problems stacking. Initially it was failing in one of the
  migrations, so I changed the SQLAlchemy version to 0.8.4 and alembic
  to 0.6.5 and retried (clean database).

  What I saw was that the migration worked, but later a router create
  failed.  It was complaining that the enable_snat field was not
  specified and did not have a default value. Checking in the
  migrations, I saw that 128e042a2b68_ext_gw_mode.py adds this field and
  sets the default value to True. However, it was not doing that.

  I changed the migration file to use server_default=sa.text("true") and
  now the migration works. BTW, it was the only migration file using
  'default=True'.

  Not sure if we should just apply this change to the existing migration
  file or if some other action is needed.

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