Red Hat Bugzilla – Bug 861708
Detach network from cluster should be possible when network is attached to VM.
Last modified: 2016-02-10 14:58:34 EST
Description of problem:
When network is attached to VM it cannot be detach from the cluster. This operation should be allowed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create network and attach it to VM.
2. Try to detach the network from the cluster.
Failed with error about network is used by VM.
Should succeed to detach the network from cluster
Argument for supporting this:
There is no difference between this and any other network, if we allow for detach of a network when there are hosts with this network connected to the cluster then we should allow it.
Note that removing the network does not remove it's configuration from the hosts so the VMs continue to operate, also note that other networks that we do allow to remove may have even more critical roles (example storage) and yet we do allow for it.
The only effect of detaching a network from a cluster is making it de-facto as non required while its detached + during this time you won't be able to create new Nic with this network attached or add it to new hosts.
What should be done is:
1. Convert the blocking to a warning - There are still VMs attached to this network are you sure?
2. Verify that VMs will actually start on hosts that have this network even if the network is not attached to the cluster but yet exist on the host. If not this should also be part of the warning - that only running VMs will continue to run.
It's should be part of the don't nanny the user policy - what ever is not destructive to current running configuration should be allowed with the proper warning.
This detaching is the only method we allow for changing network properties like MTU.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.