Bug 909820
| Summary: | [engine][networks] Don't block removing/updating network "used" by host | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Mike Kolesnik <mkolesni> |
| Component: | ovirt-engine | Assignee: | lpeer <lpeer> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Meni Yakove <myakove> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2.0 | CC: | acathrow, dyasny, iheim, lpeer, masayag, Rhev-m-bugs, sgrinber, yeylon, ykaul |
| Target Milestone: | --- | ||
| Target Release: | 3.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | network | ||
| Fixed In Version: | sf13.1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 948448 | ||
|
Description
Mike Kolesnik
2013-02-11 08:22:46 UTC
Just note this is a complex operation: 1. Remove from DC 2. Remove from all clusters 3. Remove from the configuration per all the hosts. Only then it becomes un-managed. Now for VM-Network which is assigned to VMs it may be even more complex - here we may need to block. If we don't then: If all VMs that are attached to the network are down - remove the network from all the VMs NICs and make them "None" If VMs are running, I have no idea how this could be solved. You can do as the above, but I don't see the engine sending re-wire command for each VM moving them to the null network. (In reply to comment #1) > Just note this is a complex operation: > 1. Remove from DC > 2. Remove from all clusters > 3. Remove from the configuration per all the hosts. > > Only then it becomes un-managed. > > Now for VM-Network which is assigned to VMs it may be even more complex - > here we may need to block. > > If we don't then: > If all VMs that are attached to the network are down - remove the network > from all the VMs NICs and make them "None" > If VMs are running, I have no idea how this could be solved. You can do as > the above, but I don't see the engine sending re-wire command for each VM > moving them to the null network. I'm not sure what you mean. When the network is removed from the DC, it is removed from the cluster, but remains on the host as an unmanaged network. Regarding a network that is assigned to a VM, I agree we should continue blocking network removal. (In reply to comment #2) > I'm not sure what you mean. When the network is removed from the DC, it is > removed from the cluster, but remains on the host as an unmanaged network. Yes, now that you say so, I remember that we do not have 'host configuration' saved in the DB, thus the only indication for managed/un-managed id it's existence in the cluster The problem is that it's a wrong approach and this is why it takes time for me to account for that. > Regarding a network that is assigned to a VM, I agree we should continue > blocking network removal. Behaviour of Update network will be modified as well to allow updating a network when network is assigned to a host. The network will simply become unsynced, and admin will be able to sync the network via Setup Networks. Verified on rhevm-3.2.0-10.19.beta2.el6ev.noarch 3.2 has been released 3.2 has been released 3.2 has been released |