Bug 1131856
Summary: | Failed to remove host xxxxxxxx | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | ovirt-engine | Assignee: | Arik <ahadas> |
Status: | CLOSED ERRATA | QA Contact: | Ilanit Stein <istein> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.4.0 | CC: | aburden, ahadas, asegundo, ecohen, iheim, juwu, lpeer, mavital, michal.skrivanek, mkalinin, ofrenkel, oourfali, rbalakri, Rhev-m-bugs, sherold, ukar, yeylon |
Target Milestone: | --- | Keywords: | Triaged, ZStream |
Target Release: | 3.4.3 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | virt | ||
Fixed In Version: | org.ovirt.engine-root-3.4.3-1 | Doc Type: | Bug Fix |
Doc Text: |
Previously, migrating virtual machines off a host and placing the host into maintenance mode potentially overrode the monitoring data, setting it back to it previous value. In these cases, the host was unable to be removed from the environment. Now, placing the host into maintenance mode occurs only in the after-refresh-treatment part of the monitoring, and a host in maintenance mode can be removed from the environment.
|
Story Points: | --- |
Clone Of: | 1112359 | Environment: | |
Last Closed: | 2014-10-23 12:30:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1112359 | ||
Bug Blocks: |
Comment 1
Arik
2014-08-22 07:48:25 UTC
Verified on av12.1, hosts rhel6.5. vdsm-4.14.17-1.el6ev.x86_64 libvirt-0.10.2-29.el6_5.12.x86_64 gpxe-roms-qemu-0.9.7-6.10.el6.noarch qemu-img-rhev-0.12.1.2-2.415.el6_5.14.x86_64 qemu-kvm-rhev-0.12.1.2-2.415.el6_5.14.x86_64 qemu-kvm-rhev-tools-0.12.1.2-2.415.el6_5.14.x86_64 Tried to remove host 8 times, and it was successful. Please provide the doc text if this bug requires it. Otherwise, set the require_doc_text flag to -. Many thanks, 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/RHBA-2014-1712.html |