[ovs-git] [openvswitch/ovs] 17e6ef: python: Fix attempt to use a bool as a function.

[GitHub]

  Branch: refs/heads/branch-2.4
  Home:   https://github.com/openvswitch/ovs
  Commit: 17e6ef35a02a8933b05225cd7a9482c21ae2fc84
      https://github.com/openvswitch/ovs/commit/17e6ef35a02a8933b05225cd7a9482c21ae2fc84
  Author: Sumit Garg <sumit at extremenetworks.com>
  Date:   2015-06-25 (Thu, 25 Jun 2015)

  Changed paths:
    M python/ovs/db/idl.py

  Log Message:
  -----------
  python: Fix attempt to use a bool as a function.

A bool (has_lock) was being accessed as a function call leading to a
runtime exception.

Signed-off-by: Sumit Garg <sumit at extremenetworks.com>
Signed-off-by: Ben Pfaff <blp at nicira.com>


  Commit: e2695ccb9c8d16cfc41925ef9c780b79ba1cd25d
      https://github.com/openvswitch/ovs/commit/e2695ccb9c8d16cfc41925ef9c780b79ba1cd25d
  Author: Sumit Garg <sumit at extremenetworks.com>
  Date:   2015-06-25 (Thu, 25 Jun 2015)

  Changed paths:
    M python/ovs/db/idl.py

  Log Message:
  -----------
  python: Fix writing to non-"alert" column for newly inserted row.

When 'alert' was turned off on a column, the code was erroring out when
value for that column was being set in a newly inserted row. This is
because the row._data was None at this time.

It seems that new rows are not initialized to defaults and that's why the
NULL error happens.  IMO a newly inserted row should automatically get
intialized to default values.  This new behavior can be implemented as a
separate improvement sometime in the future.

For now, I don't see an issue with adding the additional check. This new
check can continue as-is even after the new behavior is implemented.

Signed-off-by: Sumit Garg <sumit at extremenetworks.com>
Signed-off-by: Ben Pfaff <blp at nicira.com>


  Commit: db7474614d835dddc9c72c8d527a9f7f751cbb7d
      https://github.com/openvswitch/ovs/commit/db7474614d835dddc9c72c8d527a9f7f751cbb7d
  Author: Sumit Garg <sumit at extremenetworks.com>
  Date:   2015-06-25 (Thu, 25 Jun 2015)

  Changed paths:
    M python/ovs/jsonrpc.py

  Log Message:
  -----------
  python: Fix issue with probes for JSONRPC connections

When opening a JSONRPC connection, the health probes
are incorrectly getting turned off for connections
that need probes.

In other words, when stream_or_pstream_needs_probes()
return non-zero, the probes are gettting disabled as
the probe interval is getting set to zero. This leads
to incorrect behavior such that probes are:

  - not getting turned off for unix: connections
  - getting turned off for tcp:/ssl: connections

The changes in this commit fix this issue.

Signed-off-by: Sumit Garg <sumit at extremenetworks.com>
Signed-off-by: Ben Pfaff <blp at nicira.com>


Compare: https://github.com/openvswitch/ovs/compare/cb8920384fd5...db7474614d83