Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 957377

Summary:	openvswitch service not available after reboot
Product:	Red Hat OpenStack	Reporter:	Marcelo Giles <mgiles>
Component:	openvswitch	Assignee:	Thomas Graf <tgraf>
Status:	CLOSED ERRATA	QA Contact:	Rami Vaknin <rvaknin>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.0	CC:	ajeain, apevec, breeler, chrisw, rkhan, tgraf, yeylon, ykaul
Target Milestone:	rc
Target Release:	3.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openvswitch-1.9.0-2.el6ost	Doc Type:	Bug Fix
Doc Text:	Previously, the openvswitch service would not start automatically upon reboot. The service has now been added to the runlevel so openvswitch now starts automatically after a reboot, if enabled.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-27 17:15:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marcelo Giles 2013-04-27 20:16:54 UTC

Description of problem:

After installing and configuring openvswitch, if the system is powered off or rebooted, the openvswitch service will not be autostarted, as expected

Version-Release number of selected component (if applicable):
openvswitch-1.9.0-1.el6.x86_64 
How reproducible:
Always

Steps to Reproduce:
# reboot
# ovs-vsctl show
2013-04-27T19:52:27Z|00001|stream_unix|WARN|/var/run/openvswitch/db.sock: connection failed (No such file or directory)
2013-04-27T19:52:27Z|00002|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (No such file or directory)

# service openvswitch status
ovsdb-server is not running
ovs-vswitchd is not running
# chkconfig openvswitch --list
service openvswitch supports chkconfig, but is not referenced in any runlevel (run 'chkconfig --add openvswitch')
# chkconfig --add openvswitch
# chkconfig openvswitch on
# service openvswitch start
  
Actual results:
RPM scriptlet is missing the chkconfig --add routine, for example:

# rpm -q openstack-nova-scheduler --scripts
postinstall scriptlet (using /bin/sh):
/sbin/chkconfig --add openstack-nova-scheduler
...

Additional information:
RDO/Grizzly on RHEL 6.4

Comment 3 Thomas Graf 2013-06-03 14:43:42 UTC

Fixed in openvswitch-1.9.0-2.el6

Comment 6 Rami Vaknin 2013-06-18 06:47:31 UTC

Verified on grizzly running on rhel6.4 with openvswitch-1.9.0-2.el6ost.x86_64 (puddle 2013-06-13.2).

I rebooted all my env machines after packstack installation, openvswitch is up and respond to "ovs-vsctl show" command:

$ /etc/init.d/openvswitch status
ovsdb-server is running with pid 1316
ovs-vswitchd is running with pid 1326

$ ovs-vsctl show
58cdf24e-163c-4538-9eae-5d0f7888035d
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth2.185"
            Interface "eth2.185"
        Port "tap260f2d67-72"
            Interface "tap260f2d67-72"
    Bridge br-vlans
        Port br-vlans
            Interface br-vlans
                type: internal
        Port "eth2"
            Interface "eth2"
        Port phy-br-vlans
            Interface phy-br-vlans
    Bridge br-int
        Port "tapef23b7a9-82"
            tag: 2
            Interface "tapef23b7a9-82"
        Port "tap773a6b2a-c0"
            tag: 1
            Interface "tap773a6b2a-c0"
        Port "tap8f82a29a-81"
            tag: 2
            Interface "tap8f82a29a-81"
        Port br-int
            Interface br-int
                type: internal
        Port int-br-vlans
            Interface int-br-vlans
        Port "tap6603dcc0-79"
            tag: 1
            Interface "tap6603dcc0-79"
    ovs_version: "1.9.0"

Comment 7 Bruce Reeler 2013-06-20 02:54:12 UTC

Edited Doc Text for errata

Comment 9 errata-xmlrpc 2013-06-27 17:15:19 UTC

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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0968.html