db_add() as part of transaction in new object fails native interface

[Terry Wilson]

When doing something like:

    with self.ovsdb.transaction() as txn:
        txn.add(self.ovsdb.add_br(self.br_name,
                datapath_type=self.datapath_type))
        txn.add(self.ovsdb.db_add('Bridge', self.br_name,
                                  'protocols', constants.OPENFLOW10))

the native interface fails due to the 'protocols' column not yet existing on the temporary ovsdb object.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 2c7ef566af9bccbc565e0dc0259a8c456396153f
Author: Terry Wilson <email address hidden>
Date: Tue Oct 25 01:05:24 2016 -0500

    Handle db_add in transaction for new objects

    The native interface chokes when doing db_add on an object that
    was created within the same transaction due to the column we are
    modifying not yet existing. This patch adds defaults for the
    column.

    Change-Id: I4386aa293f9b18d2e17b4a80d9c7da4b9b46f3c9
    Closes-Bug: #1642764

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 10.0.0.0b2 development milestone.