* When both filters (network-id and device-id) are used, the
vnc_openstack has to compare the device-id and the network-id. Both
have to be present in the vmi_obj refs. The vnc_lib with both refs returns
a result with an OR logical operation, therefore with the current comparison
the vnc_openstack returns a result with an AND on both filters.
* Add a new conditional entry that manages the case if there is only the
network-id provided in the filters.
Change-Id: I3054345a84caeb892e85a350533e4e600f353665
Closes-Bug: #1685764
(cherry picked from commit 8ff6c714ebe4afde5613b0d3cb4d3ff0ac2ee504)
Reviewed: https:/ /review. opencontrail. org/31405 github. com/Juniper/ contrail- controller/ commit/ 1843234b248fac9 66ed21cae98109c 18a9e8532e
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: R3.2
commit 1843234b248fac9 66ed21cae98109c 18a9e8532e
Author: bfernando <email address hidden>
Date: Tue May 2 16:32:55 2017 +0200
Fix nework-id and device-id filters management
* When both filters (network-id and device-id) are used, the
vnc_openstack has to compare the device-id and the network-id. Both
have to be present in the vmi_obj refs. The vnc_lib with both refs returns
a result with an OR logical operation, therefore with the current comparison
the vnc_openstack returns a result with an AND on both filters.
* Add a new conditional entry that manages the case if there is only the
network-id provided in the filters.
Change-Id: I3054345a84caeb 892e85a350533e4 e600f353665 e5613b0d3cb4d3f f0ac2ee504)
Closes-Bug: #1685764
(cherry picked from commit 8ff6c714ebe4afd