Ah I see, thanks for the explanation. It sounds like it will likely get addressed in a future oVirt update.
On Tue, Jan 29, 2019 at 11:32 AM Dominik Holler <dhol...@redhat.com> wrote: > On Tue, 29 Jan 2019 11:16:16 -0400 > Jayme <jay...@gmail.com> wrote: > > > This command on ovirt host gives me: > > > > # ovs-vsctl --verbose=db_ctl_base:syslog:off > > ovs-vsctl: missing command name (use --help for help) > > > > Jayme, sorry for explaining incompletely. > The logging of ovs-vsctl cannot be configured by ovs-vswitchd, > only by the command line parameter --verbose of ovs-vsctl. > This basically means that the caller of ovs-vsctl has to be modified. > If the caller is oVirt/VDSM, oVirt/VDSM has to be updated. > In this particular case, this is tracked by > https://bugzilla.redhat.com/1670370 > > > > On Mon, Jan 28, 2019 at 3:35 PM Dominik Holler <dhol...@redhat.com> > > wrote: > > > > > On Mon, 28 Jan 2019 10:46:37 -0800 > > > Ben Pfaff <b...@ovn.org> wrote: > > > > > > > On Mon, Jan 28, 2019 at 05:37:36PM +0100, Dominik Holler wrote: > > > > > Is there a way to disable the error message > > > > > > > > > > ovs|00001|db_ctl_base|ERR|no key "xxx" in Open_vSwitch record > > > > > "." column external_ids > > > > > > > > > > in syslog? > > > > > ovs-appctl vlog/set seems not to know about db_ctl_base. > > > > > > > > This message doesn't come from ovs-vswitchd, so "ovs-appctl > > > > vlog/set" won't help. Use the -v command line option to whatever > > > > utility you're running. > > > > > > Thanks, for me > > > ovs-vsctl --verbose=db_ctl_base:syslog:off > > > did the trick. > > > > >
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss