Bug 1332857

Summary: Adding ovirtmgmt logical network takes indefinitely
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: BLL.NetworkAssignee: Dan Kenigsberg <danken>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: bugs, danken, ylavi
Target Milestone: ovirt-4.0.0-betaKeywords: Reopened
Target Release: 4.0.0Flags: rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-05 08:04:52 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 log none

Description Petr Matyáš 2016-05-04 08:47:05 UTC
Created attachment 1153748 [details]
engine log

Description of problem:
When I try to add ovirtmgmt logical network to hosts network interface, saving this setup takes indefinitely.

Version-Release number of selected component (if applicable):
ovirt-engine-4.0.0-0.0.master.20160502051351.git5a04b83.el7.centos.noarch

How reproducible:
always

Steps to Reproduce:
1. install host
2. try to add ovirtmgmt logical network to hosts network interface
3.

Actual results:
saving takes indefinitely

Expected results:
ovirtmgmt logical network setted up correctly

Additional info:
2016-05-04 08:35:15,397 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-3) [2c6fcf79] START, HostSetupNetwork
sVDSCommand(HostName = 10.34.60.46, HostSetupNetworksVdsCommandParameters:{runAsync='true', hostId='effcdffa-588c-43fb-a89d-00a34a1f9478', vds='Host[10.3
4.60.46,effcdffa-588c-43fb-a89d-00a34a1f9478]', rollbackOnFailure='true', connectivityTimeout='120', networks='[HostNetwork:{defaultRoute='true', bonding
='false', networkName='ovirtmgmt', nicName='eth0', vlan='null', mtu='0', vmNetwork='true', stp='false', properties='null', ipv4BootProtocol='DHCP', ipv4A
ddress='null', ipv4Netmask='null', ipv4Gateway='null', ipv6BootProtocol='DHCP', ipv6Address='null', ipv6Prefix='null', ipv6Gateway='null'}]', removedNetw
orks='[]', bonds='[]', removedBonds='[]'}), log id: 5c28b226

Comment 1 Dan Kenigsberg 2016-05-04 13:29:19 UTC

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

Comment 2 Petr Matyáš 2016-05-06 14:38:10 UTC
This bug is for 4.0, not 3.6. So bug 1329317 can't be duplicate of this one, although it might be the same issue.

Comment 3 Petr Matyáš 2016-05-16 07:24:38 UTC
Verified on ovirt-engine-4.0.0-0.0.master.20160515171411.git6759e3f.el7.centos.noarch

Comment 4 Yaniv Kaul 2016-05-19 08:49:43 UTC
Dan - which target milestone?

Comment 5 Red Hat Bugzilla Rules Engine 2016-05-19 11:58:37 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 6 Sandro Bonazzola 2016-07-05 08:04:52 UTC
oVirt 4.0.0 has been released, closing current release.