yahoo-eng-team team mailing list archive

[Terry Wilson <1615105@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The OVSDB native and vsctl implementations return different types of
results for db_create(). The native implementation returns a Row()
object, which is specific to using OVS's python library. The vsctl
implementation returns a string representation of the created uuid. Even
with --format=json, the returned result is not JSON.

To be uniform, both implementations should return a uuid.UUID object
representing the uuid assigned to the newly inserted row.

The db_create call isn't currently used by neutron, but patch
https://review.openstack.org/#/c/341186/ makes use of it.

** Affects: neutron
     Importance: Undecided
     Assignee: Terry Wilson (otherwiseguy)
         Status: In Progress

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

Title:
  ovsdb's db_create results not uniform across vsctl and native
  implementations

Status in neutron:
  In Progress

Bug description:
  The OVSDB native and vsctl implementations return different types of
  results for db_create(). The native implementation returns a Row()
  object, which is specific to using OVS's python library. The vsctl
  implementation returns a string representation of the created uuid.
  Even with --format=json, the returned result is not JSON.

  To be uniform, both implementations should return a uuid.UUID object
  representing the uuid assigned to the newly inserted row.

  The db_create call isn't currently used by neutron, but patch
  https://review.openstack.org/#/c/341186/ makes use of it.

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