Bug 1059482
Summary: | Migrating between older and newer RHEV-H images leads to flood "path /rhev/data-center/mnt/blockSD/<UUID>/images/<UUID>/<UUID> not assigned to domain" | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | David Gibson <dgibson> | |
Component: | vdsm | Assignee: | Federico Simoncelli <fsimonce> | |
Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 3.3.0 | CC: | abisogia, bazulay, cpelland, danken, eedri, fsimonce, gchakkar, gwatson, iheim, jcoscia, jraju, lbopf, lpeer, mbourvin, meverett, mhuth, michal.skrivanek, michele, mkalinin, mtessun, pablo.iranzo, rmcswain, sbonazzo, scohen, tcarlin, tvvcox, usurse, yeylon | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | 3.4.0 | Flags: | scohen:
needinfo+
scohen: needinfo+ |
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | storage | |||
Fixed In Version: | ovirt-3.4.0-beta3 | Doc Type: | Bug Fix | |
Doc Text: |
An update to VDSM changed a path used by libvirt. Consequently, logs were flooded with messages about invalid paths. The virtual machines associated with these logs worked, but migrations from older RHEV-H to newer RHEV-H caused the logs to flood.
An update to VDSM adjusts the libvirt XML to match the form the destination is using after a migration from an older version of RHEV-H to a newer version of RHEV-H.
Now, logs are no longer flooded with messages about invalid paths.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1061621 (view as bug list) | Environment: | ||
Last Closed: | 2014-06-09 13:28:32 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1061621, 1078909, 1094944, 1142926 |
Description
David Gibson
2014-01-29 23:07:17 UTC
In fact, fixing only for 3.4.0 could actually be *worse* than not fixing it at all. Because the problem is a mismatch in behaviour between hypervisor versions, just reverting the behaviour in 3.4 would cause this problem to occur again for all those people who've switched to the current behaviour in the interim, and restarted their VMs to work around the errors. A real fix would need to check for this situation during migrate, and adjust the libvirt XML to match whatever form the destination vdsm is using. @Ulhas, Which workaround from the KCS? Restarting the VM, or migrating back to the old vdsm? David, It's restart the VM. 2) Otherwise if the VM can be shutdown then shut it down on the vdsm 4.13.2-0.6 hypervisor and start it again. Note it must be shutdown completely and not simply rebooted. *** Bug 1055437 has been marked as a duplicate of this bug. *** Tested with two RHEVH nodes and 3.4 management. First RHEVH - RHEL 6.4 with vdsm-4.10.2-25.1.el6ev Second RHEVH - RHEL 6.5 with vdsm-4.13.2-0.6.el6ev. VM migrated from the first rhevh to the second one and vise versa. No error appear in vdsm.log. 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. http://rhn.redhat.com/errata/RHBA-2014-0504.html |