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

Bug 1587962

Summary: openvswitch service is not started when adding host to ovs cluster which has no OVN provider
Product: [oVirt] ovirt-engine Reporter: Leon Goldberg <lgoldber>
Component: Host-DeployAssignee: Leon Goldberg <lgoldber>
Status: CLOSED CURRENTRELEASE QA Contact: msheena
Severity: low Docs Contact:
Priority: medium    
Version: 4.2.0CC: bugs, danken, lsvaty, mburman
Target Milestone: ovirt-4.2.5Flags: 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: 2018-07-31 15:32:21 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:
Attachments:
Description Flags
VDSM log none

Description Leon Goldberg 2018-06-06 11:13:07 UTC
Created attachment 1448290 [details]
VDSM log

Description of problem:
Adding a host to an OVS cluster fails due to ovirtmgmt not being able to be created. OVS' database socket is not created because the service is not launched.

Version-Release number of selected component (if applicable):
4.30.0-405.git7b1e239.el7

How reproducible:
100%

Steps to Reproduce:
1. Create cluster, use OVS switch.
2. Add host to the cluster.

Actual results:
Host addition fails.

Expected results:
Host addition succeeds.

Comment 1 Red Hat Bugzilla Rules Engine 2018-07-19 09:04:16 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 msheena 2018-07-25 08:14:15 UTC
verified on:
4.2.5.2-0.1.el7ev

Comment 3 Sandro Bonazzola 2018-07-31 15:32:21 UTC
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.5 release, it has been closed with a resolution of CURRENT RELEASE.

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