Bug 1247037

Summary:	[new HostSetupNetworks] unmanaged networks handling
Product:	[oVirt] ovirt-engine	Reporter:	Alona Kaplan <alkaplan>
Component:	General	Assignee:	Marcin Mirecki <mmirecki>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	high
Version:	---	CC:	bugs, danken, ecohen, gklein, lsurette, mmucha, rbalakri, yeylon, ylavi
Target Milestone:	ovirt-3.6.1	Flags:	ylavi: ovirt-3.6.z? ylavi: ovirt-4.0.0? ylavi: blocker? ylavi: planning_ack? ylavi: devel_ack? ylavi: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-26 14:39:38 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:

Description Alona Kaplan 2015-07-27 07:59:25 UTC

Description of problem:

1. When detaching network from cluster- the network attachments of the network are not removed.
2. Any operation with unmanaged networks, except removing it, should be blocked.
(Moving to another nic, adding network to the nic that contains unmanaged network, adding nic with unmanaged network to a bond).

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Alona Kaplan 2015-07-27 08:56:02 UTC

Also attaching a label to nic with unmanaged networks should be blocked.

Comment 2 Alona Kaplan 2015-07-28 12:12:38 UTC

Also, when attaching a network to cluster, in case previously the network was unmanaged on the host. And attachment should be added.

Comment 3 Yaniv Lavi 2015-09-07 09:15:21 UTC

should this be MODIFIED?

Comment 4 Dan Kenigsberg 2015-09-10 11:26:03 UTC

I'm afraid not -

2. Any operation with unmanaged networks, except removing it, should be blocked.
(Moving to another nic, adding network to the nic that contains unmanaged network, adding nic with unmanaged network to a bond).

is not implemented yet.

Comment 7 Martin Mucha 2015-09-15 20:24:43 UTC

Current status:
ad 1 — this was already fixed, but due to error in "manage networks" dialog it cannot be verified.

ad 2 — in UI, which uses new command,  it seems that:
• moving is illegal
• adding another network to same nic is illegal
• adding nic which has unmanaged network to bond is illegal.

via old command I did not test it. Should be old command tested and fixed if needed?

via rest & new command:
• moving cannot be performed since unmanaged network does not have relevant network attachment.
• adding another network to nic which contains unmanaged network is allowed
• creating bond using as a slave nic which has unmanaged network is allowed.

--> ie. not speaking about old command, there are two bugs to be solved. Two new validation methods needs to be introduced, I'll solve both using this patch and two distinct changes.

Comment 8 Dan Kenigsberg 2015-09-24 07:37:45 UTC

since sub-issue (1) was solved, we can demote the "blocker" status of this bug.

Comment 9 Red Hat Bugzilla Rules Engine 2015-10-19 10:50:34 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 10 Dan Kenigsberg 2015-10-26 14:39:38 UTC

let us consider sub-issue(2) only once

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