On 07/25/2017 12:23 AM, Gurucharan Shetty wrote:
ovs-bugtool collects a lot of data. This can be time
consuming and can end up collecting a lot of redundant data.
A option "--ovs" was added a while ago to only collect
OVS relevent data. We missed adding the OVS logs to this
filter.
Signed-off-by: Gurucharan Shetty <[email protected]>
---
utilities/bugtool/ovs-bugtool.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/utilities/bugtool/ovs-bugtool.in b/utilities/bugtool/ovs-bugtool.in
index 5eb3440..b47d9a4 100755
--- a/utilities/bugtool/ovs-bugtool.in
+++ b/utilities/bugtool/ovs-bugtool.in
@@ -659,7 +659,7 @@ exclude those logs from the archive.
if only_ovs_info:
filters.add('ovs')
ovs_info_caps = [CAP_NETWORK_STATUS, CAP_SYSTEM_LOGS,
- CAP_NETWORK_CONFIG]
+ CAP_OPENVSWITCH_LOGS, CAP_NETWORK_CONFIG]
ovs_info_list = ['process-tree']
# We cannot use iteritems, since we modify 'data' as we pass through
for (k, v) in data.items():
Reviewed-by: Greg Rose <[email protected]>
Tested-by: Greg Rose <[email protected]>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
