Migration pool_monitor_status fails when database already contains data

[Eugene Nikanorov]

In case Healthmonitmonitor tables already contain data, migration 11c6e18605c8_pool_monitor_status fails with the following traceback:

http://paste.openstack.org/show/75388/

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/86548

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/86548
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c7dceedde516170d1a6ac1257103bdacb3b0cc84
Submitter: Jenkins
Branch: master

commit c7dceedde516170d1a6ac1257103bdacb3b0cc84
Author: Eugene Nikanorov <email address hidden>
Date: Thu Apr 10 13:36:45 2014 +0400

    Properly apply column default in migration pool_monitor_status

    server_default parameter should be used to apply default value at
    table/column creation time. Otherwise non-nullable column can't
    be created because of existing rows in the tables.

    Change-Id: I7136e6a0dfb9dc66ca63ff3c9fcf6de164e27e63
    Closes-Bug: #1305725