[ovirt-users] OVS error logs after upgrade to 4.2

[Misak Khachatryan]

Hello Marcin,

Thank you for the info!

Best regards,
Misak Khachatryan


On Thu, Dec 28, 2017 at 4:26 PM, Marcin Mirecki <mmirecki at redhat.com> wrote:
> Hello Misak,
>
> The openvswitch team tells me this is a known ovs problem.
> It is fixed by patch:
> https://github.com/openvswitch/ovs/commit/bbf219ef584a102fde5150defab3a769a6a44981
> merged in master/branch 2.8/branch 2.7.
> Looking at git history this is not yet released. It should be included in
> 2.7.4 when it's out.
>
> Thanks,
> Marcin
>
>
>
> On Thu, Dec 28, 2017 at 10:53 AM, Misak Khachatryan <kmisak at gmail.com>
> wrote:
>>
>> Hi Mor,
>>
>> submitted: https://bugzilla.redhat.com/show_bug.cgi?id=1529481
>>
>> I've collected logs but they are 1662.7M in size.
>>
>> Best regards,
>> Misak Khachatryan
>>
>>
>> On Wed, Dec 27, 2017 at 6:44 PM, Mor Kalfon <mkalfon at redhat.com> wrote:
>> > Hello Misak,
>> >
>> > Could you please file a bug about those error messages that you receive
>> > from
>> > OVS?
>> > You can use the log collector tool
>> >
>> > (https://www.ovirt.org/documentation/admin-guide/chap-Utilities/#the-log-collector-tool)
>> > which gathers all the required logs for us to investigate this issue.
>> >
>> > Thanks for reporting this issue!
>> >
>> > On Wed, Dec 27, 2017 at 11:03 AM, Misak Khachatryan <kmisak at gmail.com>
>> > wrote:
>> >>
>> >> On Wed, Dec 27, 2017 at 12:42 PM, Dan Kenigsberg <danken at redhat.com>
>> >> wrote:
>> >> > On Wed, Dec 27, 2017 at 8:49 AM, Misak Khachatryan <kmisak at gmail.com>
>> >> > wrote:
>> >> >> Hi,
>> >> >>
>> >> >> It's not on log file, it's from automatic email sent by cron daemon.
>> >> >> This one from logrotate.
>> >> >
>> >> > Would you file a bug about this daily logrotate spam?
>> >> >
>> >>
>> >> Sure, will do.
>> >>
>> >> >>
>> >> >> I'd like to migrate my network to OVS, but as i can't find any guide
>> >> >> for that, it's a bit scary.
>> >> >
>> >> > Why would you like to do that? OVN is useful for big deployments,
>> >> > that
>> >> > have many isolated networks. It is not universally recommended, as it
>> >> > uses more CPU.
>> >> >
>> >>
>> >> No particular reason, thought that will be future in oVIRT networking,
>> >> also i work in relatively big ISP with many PoP and DCs in many
>> >> cities. And I'm interested to try it some time.
>> >>
>> >> >>
>> >> >> Best regards,
>> >> >> Misak Khachatryan
>> >> >>
>> >> >>
>> >> >> On Tue, Dec 26, 2017 at 3:29 PM, Dan Kenigsberg <danken at redhat.com>
>> >> >> wrote:
>> >> >>> On Tue, Dec 26, 2017 at 8:35 AM, Misak Khachatryan
>> >> >>> <kmisak at gmail.com>
>> >> >>> wrote:
>> >> >>>> Hi,
>> >> >>>>
>> >> >>>> After upgrade to 4.2 I started getting this error from engine:
>> >> >>>>
>> >> >>>> /etc/cron.daily/logrotate:
>> >> >>>>
>> >> >>>> 2017-12-25T23:12:02Z|00001|unixctl|WARN|failed to connect to
>> >> >>>> /var/run/openvswitch/ovnnb_db.19883.ctl
>> >> >>>> ovs-appctl: cannot connect to
>> >> >>>> "/var/run/openvswitch/ovnnb_db.19883.ctl" (No such file or
>> >> >>>> directory)
>> >> >>>> 2017-12-25T23:12:02Z|00001|unixctl|WARN|failed to connect to
>> >> >>>> /var/run/openvswitch/ovnsb_db.19891.ctl
>> >> >>>> ovs-appctl: cannot connect to
>> >> >>>> "/var/run/openvswitch/ovnsb_db.19891.ctl" (No such file or
>> >> >>>> directory)
>> >> >>>>
>> >> >>>>
>> >> >>>> Seems harmless as i don't use OVS, but how to fix it?
>> >> >>>
>> >> >>> By default, ovirt-4.2 installs and configure OVN (which uses OVS).
>> >> >>> You
>> >> >>> can turn it off on Engine host by running
>> >> >>> systemctl stop ovirt-provider-ovn ovn-northd openvswitch
>> >> >
>> >> > did you try that?
>> >> >
>> >>
>> >> No, but is correct way to disable it completely?
>> >>
>> >> >>>
>> >> >>> but I'd appreciate your help to understand in which log file do you
>> >> >>> see these warnings?
>> >> >
>> >> >>> Have you already disabled openvswitch?
>> >> >
>> >> > have you ^^ ?
>> >>
>> >> No, what is a correct way to do it?
>> >
>> >
>> >
>> >
>> > --
>> > Mor Kalfon
>> > RHV Networking Team
>> > Red Hat IL-Raanana
>> > Tel: +972-54-6514148
>> >
>
>