-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
?
-
?
-
?
-
?
-
None
-
-
-
Important
Since https://issues.redhat.com/browse/OSPRH-6326 ovs-vswitchd container(ovn-controller-ovs pods) not logging to console as it starts the ovs-vswitchd in detach mode and from the man page:-
Runs as a background process. The process forks, and in
the child it starts a new session, closes the standard file
descriptors (which has the side effect of disabling logging to the
console), and changes its current directory to the root (unless
--no-chdir is specified). After the child completes its
initialization, the parent exits.
Noticed while looking into https://issues.redhat.com/browse/OSPRH-10821
– Notes from the triage call –
/usr/sbin/ovs-vswitchd --pidfile --mlockall --detach
We need a different way of running ovs-vswitchd on a different thread so as to not block the flow restoration performed by this same script.
- is caused by
-
-
- Verified
-
