Bug 1490938

Summary:	OVS/OVN services should be started on OVN hosts
Product:	[oVirt] ovirt-provider-ovn	Reporter:	Mor <mkalfon>
Component:	provider	Assignee:	Marcin Mirecki <mmirecki>
Status:	CLOSED DUPLICATE	QA Contact:	Mor <mkalfon>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1.0.4	CC:	bugs, danken, mkalfon, ylavi
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-13 08:39:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mor 2017-09-12 14:14:49 UTC

Description of problem:
On the recent upgrade to OpenVSwitch 2.7.2, OVS services should be started and enabled on OVN hosts. Currently, the services ship as disabled and inactive, requiring a manual change to enable and start them. This could be accomplished using 'vdsm-tool ovn-config' command (if it will start them as a prerequisite).

Version-Release number of selected component (if applicable):
Red Hat Virtualization Manager Version: 4.1.6.2-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1. Install RHV 4.1 environment (ovirt-engine and at lest one host).
2. Check the services state using 'systemctl status <service>' for each OVS/OVN service that is required for ovirt-provider-ovn-driver.

Actual results:
Should be enabled and started.

Expected results:
Not enabled and not started.

Comment 1 Dan Kenigsberg 2017-09-13 07:45:40 UTC

Please supply /var/log/message. and output of vdsm-tool.

vdsm-tool ovn-config still has


systemctl enable openvswitch
systemctl enable ovn-controller

systemctl restart openvswitch
systemctl restart ovn-controller

Comment 2 Mor 2017-09-13 08:27:23 UTC

(In reply to Dan Kenigsberg from comment #1)
> Please supply /var/log/message. and output of vdsm-tool.
> 
> vdsm-tool ovn-config still has
> 
> 
> systemctl enable openvswitch
> systemctl enable ovn-controller
> 
> systemctl restart openvswitch
> systemctl restart ovn-controller

As I already mentioned in the bug description, if we intend to relay on vdsm-tool , then we should first fix: https://bugzilla.redhat.com/show_bug.cgi?id=1490104.

Comment 3 Dan Kenigsberg 2017-09-13 08:39:27 UTC

Yes, we must make sure ovn-config works out of the box.

*** This bug has been marked as a duplicate of bug 1490104 ***