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

Bug 1466169

Summary:	ovn-controller is not configured to start at boot
Product:	[oVirt] ovirt-provider-ovn	Reporter:	Mor <mkalfon>
Component:	provider	Assignee:	Marcin Mirecki <mmirecki>
Status:	CLOSED DUPLICATE	QA Contact:	Mor <mkalfon>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	1.0.4	CC:	bugs, danken, ylavi
Target Milestone:	---
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-06-29 08:29:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mor 2017-06-29 08:15:41 UTC

Description of problem:
ovn-controller service is not shipped as enabled (to start at boot), by thus can cause a VM to fail if it has OVN network attached to it after a reboot to the hypervisor.

Version-Release number of selected component (if applicable):
openvswitch-2.7.0-1.el7.x86_64
openvswitch-ovn-host-2.7.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. on hypervisor, run yum install openvswitch-ovn-host
2. systemctl status ovn-controller

Actual results:
Loaded: loaded (/usr/lib/systemd/system/ovn-controller.service; disabled; vendor preset: disabled)

Expected results:
ovn-controller should be enabled by the RPM installation.

Comment 1 Mor 2017-06-29 08:16:24 UTC

*** Bug 1464867 has been marked as a duplicate of this bug. ***

Comment 2 Mor 2017-06-29 08:29:10 UTC


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