ovs-vsctl fails with Protocol error until restarted

Bug #1453062 reported by Michał Sawicz on 2015-05-08
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openvswitch (Ubuntu)
High
Unassigned

Bug Description

Having deployed vivid-kilo-proposed with openstack-charm-testing, I'm initially unable to launch instances, because ovs-vsctl errors out:
ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (Protocol error)

Restarting openvswitch-switch resolves the issue:
$ juju ssh nova-compute/0 sudo systemctl restart openvswitch-switch.service

See attached a nova-compute.log from one of the units where this failed.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: openvswitch-switch 2.3.1-0ubuntu1
ProcVersionSignature: User Name 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Fri May 8 09:19:37 2015
Ec2AMI: ami-00000360
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.medium
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
SourcePackage: openvswitch
UpgradeStatus: No upgrade log present (probably fresh install)

Michał Sawicz (saviq) wrote :
summary: - ovs-vctl fails with Protocol error until restarted
+ ovs-vsctl fails with Protocol error until restarted
Matt Fischer (mfisch) wrote :

I have the same issue except I'm installing with puppet not juju and I'm using Ubuntu Cloud Archive:

root@openstack-puppet-test:/var/log/openvswitch# apt-cache policy openvswitch-switch
openvswitch-switch:
  Installed: 2.4.0-0ubuntu4~cloud0
  Candidate: 2.4.0-0ubuntu4~cloud0
  Version table:
 *** 2.4.0-0ubuntu4~cloud0 0
        500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ trusty-updates/liberty/main amd64 Packages
        100 /var/lib/dpkg/status

Changed in openvswitch (Ubuntu):
status: New → Confirmed
Matt Fischer (mfisch) on 2015-12-11
Changed in openvswitch (Ubuntu):
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers