Description of problem: If you remove network attached to Host NIC with Network labels feature from DC level, you get unmanaged network with message: Unmanaged Network doesn't exist in Cluster. Though this is a true message, when removing the network from the Cluster level only, the network doesn't become unmanaged on Host, but it disappears, so the only possibility to get unmanaged network on Host with Network label is to remove it from the DC level. That's why the message should be changed to Network doesn't exists on DC and Cluster level. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Attach network to Host by putting the same Network label on both 2. Remove network from DC 3. Actual results: The network becomes unmanaged with incorrect error message Expected results: The message should be Unmanaged Network doesn't exist in Cluster and DC Additional info:
I am less concerned about the error message, and more concerned about the inconsistent results of these two scenarios: 1. First removing network from cluster, then from DC. 2. Remove network directly from DC (and therefore from underlying clusters). In my opinion, these two scenarios should produce identical results, yet from Genadi's description it sounds like (1) removes the network from hosts whereas (2) leaves it as unmanaged.
When a network doesn't have a label, then the behavior is consistent when removing it either from a DC or from a cluster - it stays on the hosts and becomes unmanaged. When the same operations are performed for a network with a label, I think the result should be the same - it is unclear to me why when removing from a cluster, we strip the label from the network first. If we do want to maintain this behavior (although I find it confusing), I think we should do the same when removing a labelled network from a DC.
(In reply to Lior Vernia from comment #2) > When a network doesn't have a label, then the behavior is consistent when > removing it either from a DC or from a cluster - it stays on the hosts and > becomes unmanaged. > > When the same operations are performed for a network with a label, I think > the result should be the same - it is unclear to me why when removing from a > cluster, we strip the label from the network first. > > If we do want to maintain this behavior (although I find it confusing), I > think we should do the same when removing a labelled network from a DC. +1 for removing a network from hosts when the network is labelled. I suggest to extend the "remove network" flow to contain "remove from hosts" property, and let the user if he wishes to preserve or not the networks. We can have the same for "detach network from cluster" in order to achieve the symmetry.
Good, so when removing a labelled network from a DC let's make the behavior consistent with removal from clusters. Then, when we solve Bug 1062610, the desired behavior (leave unmanaged or remove from hosts) could be chosen whether the network had been labelled or not.
fixed in vt3, moving to on_qa. if you believe this bug isn't released in vt3, please report to rhev-integ
rhevm-3.5.0-0.12.beta.el6ev.noarch
Hi Martin, Please provide the doc text. Cheers, Julie
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/RHSA-2015-0158.html