-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
2
-
False
-
-
False
-
?
-
rhos-connectivity-neutron
-
None
-
-
-
-
Priority Bugs
-
1
-
Moderate
Noticed while looking a Customer case, edpm nodes logs are filled with :-
ERROR 06:43:02 appctl.go:144: Failed to get PID for ovn-northd: no control socket files found for ovn-northd ERROR 06:43:02 appctl.go:144: Failed to get PID for ovn-northd: no control socket files found for ovn-northd ERROR 06:43:02 appctl.go:131: Failed to prepare call to ovsdb-server: no control socket files found for the ovs db server ERROR 06:43:32 appctl.go:131: Failed to prepare call to ovsdb-server: no control socket files found for the ovs db server ERROR 06:43:32 appctl.go:144: Failed to get PID for ovn-northd: no control socket files found for ovn-northd ERROR 06:43:32 appctl.go:144: Failed to get PID for ovn-northd: no control socket files found for ovn-northd
In FR4 we had added support for northd/ovndbs, northd and ovndbs runs on control plane so on edpm nodes they do not run so these collectors need not be enabled. But by default we enable all the collectors on EDPM nodes. We should avoid dumping these irrelevant logs continuously on each scrape call.
