Description of problem: We log daemon output upstream, which helps us identify nbctl cmds issued. We should also be logging it downstream.
@rbrattai Can you help verifying it?
-f --retry is --follow=descriptor --retry whereas the usual -F is --follow=name --retry -f, --follow[={name|descriptor}] output appended data as the file grows; an absent option argument means 'descriptor' We usually want --follow=name, is there a reason we are only following descriptor. Also, do we want --pid=$(cat /var/run/ovn/ovn-nbctl.pid) as in the other tail commands to stop the tail once the daemon stops?
I guess --pid won't work if there is a delay in starting ovn-nbctl and the pid file doesn't exist.
Verified on 4.7.0-0.nightly-2020-12-18-031435
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633