[Bug 1050896] New: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory)

newer
[Bug 1081830] VUL-1: libid3tag0:...

bugzilla_noreply＠novell.com

27 Jul 2017 27 Jul '17

07:54

http://bugzilla.suse.com/show_bug.cgi?id=1050896 Bug ID: 1050896 Summary: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: holger@fam-schranz.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After upgrade from Leap 42.2 with openvswitch 2.5.1 to Leap 42.3 with openvswitch 2.7.0 it is not possible to work with openvswitch 2.7.0. The following error occur: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory). Old-Version (leap 42.2): ovs-vsctl --version ovs-vsctl (Open vSwitch) 2.5.1 Compiled DB Schema 7.12.1 New-Version (Leap 42.3): ETCSVMS5:~ # ovs-vsctl --version ovs-vsctl (Open vSwitch) 2.7.0 DB Schema 7.14.0 ETCSVMS5:~ # ovs-vsctl list-br ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) ETCSVMS5:~ # ovs-vsctl show ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) WorkAround: It is necessary to restart openvswitchwith systemctl enable openvswitch and start again. ETCSVMS5:~ # systemctl status openvswitch ? openvswitch.service - Open vSwitch Loaded: loaded (/usr/lib/systemd/system/openvswitch.service; disabled; vendor preset: disabled) Active: inactive (dead) ETCSVMS5:~ # systemctl enable openvswitch Created symlink from /etc/systemd/system/multi-user.target.wants/openvswitch.service to /usr/lib/systemd/system/openvswitch.service. ETCSVMS5:~ # systemctl start openvswitch ETCSVMS5:~ # ovs-vsctl show 5219890d-7cdc-4a70-9544-48bfeb365eca Bridge "S5ovs84M1I" Port "S5ovs84M1I" Interface "S5ovs84M1I" type: internal Bridge "S5ovs84M2I" Port "S5ovs84M2I" Interface "S5ovs84M2R1S2" type: internal ovs_version: "2.7.0" Should be done automatically with the update. -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 3.9 KB)

Show replies by date

bugzilla_noreply＠novell.com

27 Jul 27 Jul

11:20

New subject: [Bug 1050896] ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory)

http://bugzilla.suse.com/show_bug.cgi?id=1050896 Chenzi Cao changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |markos.chandras@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:49

New subject: [Bug 1050896] ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory)

bugzilla_noreply＠novell.com

12:38

New subject: [Bug 1050896] ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory)

http://bugzilla.suse.com/show_bug.cgi?id=1050896 http://bugzilla.suse.com/show_bug.cgi?id=1050896#c1 Markos Chandras changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #1 from Markos Chandras --- Thank you for the report. Yes, this is a problem in the leap 42.2 package since the postun() rpm scriptlet does indeed restart the service. There should be an update coming from the SLE package. I will check it's status since it should have been arrived by now. However, that fix alone is not enough. Between 2.5 and 2.7 the openvswitch-switch package has been removed so the service stops because it thinks that he package has been uninstalled (which is right) but the service should still remain active since it's now owned by a new package. I will submit a fix to SLE about this and it should arrive to 42.2 in the near future -- You are receiving this mail because: You are on the CC list for the bug.