Bug 1344355

Summary: Add hosts fails for network conf issue
Product: Red Hat Enterprise Virtualization Manager Reporter: gshinar
Component: ovirt-engineAssignee: Yevgeny Zaspitsky <yzaspits>
Status: CLOSED ERRATA QA Contact: Michael Burman <mburman>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: eedri, gklein, lsurette, mburman, mperina, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ovirt-4.0.0-rc2   
Target Release: 4.0.0   
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: 2016-08-23 20:41:59 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
engine logs
none
VDSM logs none

Description gshinar 2016-06-09 13:14:47 UTC 
Description of problem:
After installing engine, add hosts fails with the error message of:
Failed to configure management network on the host

Version-Release number of selected component (if applicable):


How reproducible:
 

Steps to Reproduce:
1. Log into engine UI.
2. Click on hosts tab
3. Press on new button
4. Fill all needed fields
5. Press ok

Actual results:
host fails to configure with the above error message

Expected results:
New host should be up and running

Additional info:
Logs shows that it is not during setup network procedure.
It doesn't get to that.
Comment 2 gshinar 2016-06-09 13:16:45 UTC 
Created attachment 1166293 [details]
engine logs
Comment 3 gshinar 2016-06-09 13:17:32 UTC 
Created attachment 1166294 [details]
VDSM logs
Comment 4 Martin Perina 2016-06-10 15:11:49 UTC 
Setting target release to 4.0.0 as it's included in today's 4.0.0.4 build
Comment 5 Michael Burman 2016-06-13 08:01:02 UTC 
Verified on - 4.0.0.4-0.1.el7ev
Comment 7 errata-xmlrpc 2016-08-23 20:41:59 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.

https://rhn.redhat.com/errata/RHEA-2016-1743.html