Bug 1466169 - ovn-controller is not configured to start at boot
Summary: ovn-controller is not configured to start at boot
Keywords:
Status: CLOSED DUPLICATE of bug 1466181
Alias: None
Product: ovirt-provider-ovn
Classification: oVirt
Component: provider
Version: 1.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Marcin Mirecki
QA Contact: Mor
URL:
Whiteboard:
: 1464867 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-29 08:15 UTC by Mor
Modified: 2017-06-29 08:29 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-06-29 08:29:10 UTC
oVirt Team: Metrics
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.