Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Previously, issues in the VDSM caused some virtual machines to become non-responsive when attempting to upgrade pools from Red Hat Enterprise Virtualization Manager 3.0 to 3.1. This has now been fixed to ensure no virtual machines will become unresponsive when upgrading.
Created attachment 625477[details]
backend and vdsm logs
Description of problem:
when upgrading the pool from V2 to V3 (rhevm 3.0 to rhevm 3.1) some of the vms become non responsive.
Version-Release number of selected component (if applicable):
vdsm-4.9.6-37.0.el6_3.x86_64
si20
How reproducible:
100%
Steps to Reproduce:
1. create and run vm's with OS installed on 3.0 pool on multiple domains (I used 5 data domains, 1 export and 1 iso).
2. upgrade to 3.1 pool
3.
Actual results:
some of the vm's become non responsive -> up and back again.
Expected results:
vm's should not become non responsive
Additional info: logs attached
UUID of one of the vms: 9d714ca2-75af-427a-8aaf-1f3afab74af3
Thread-484::ERROR::2012-10-11 10:16:49,996::task::853::TaskManager.Task::(_setError) Task=`3454f584-ab39-4956-bf67-910dc0a25c27`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 861, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
res = f(*args, **kwargs)
File "/usr/share/vdsm/storage/hsm.py", line 2603, in getVolumeSize
vars.task.getSharedLock(STORAGE, sdUUID)
File "/usr/share/vdsm/storage/task.py", line 1306, in getSharedLock
self.resOwner.acquire(namespace, resName, resourceManager.LockType.shared, timeout)
File "/usr/share/vdsm/storage/resourceManager.py", line 706, in acquire
raise se.ResourceTimeout()
ResourceTimeout: Resource timeout: ()
Thread-484::DEBUG::2012-10-11 10:16:49,998::task::872::TaskManager.Task::(_run) Task=`3454f584-ab39-4956-bf67-910dc0a25c27`::Task._run: 3454f584-ab39-4956-bf67-910dc0a25c27 ('dbed4cf3-a177-49a8-b41c-f12b85db4286', '11d18980-5c97-40ca-b7ff-6d1fa0f01cc8', '65f8e99b-7ee1-4020-8c23-431e3bf81242', '4f8feffd-ac58-4e4b-80b0-e50491aefb45') {} failed - stopping task
Comment 3Federico Simoncelli
2012-10-12 16:13:38 UTC
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/RHSA-2012-1508.html
Created attachment 625477 [details] backend and vdsm logs Description of problem: when upgrading the pool from V2 to V3 (rhevm 3.0 to rhevm 3.1) some of the vms become non responsive. Version-Release number of selected component (if applicable): vdsm-4.9.6-37.0.el6_3.x86_64 si20 How reproducible: 100% Steps to Reproduce: 1. create and run vm's with OS installed on 3.0 pool on multiple domains (I used 5 data domains, 1 export and 1 iso). 2. upgrade to 3.1 pool 3. Actual results: some of the vm's become non responsive -> up and back again. Expected results: vm's should not become non responsive Additional info: logs attached UUID of one of the vms: 9d714ca2-75af-427a-8aaf-1f3afab74af3 Thread-484::ERROR::2012-10-11 10:16:49,996::task::853::TaskManager.Task::(_setError) Task=`3454f584-ab39-4956-bf67-910dc0a25c27`::Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 861, in _run return fn(*args, **kargs) File "/usr/share/vdsm/logUtils.py", line 38, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 2603, in getVolumeSize vars.task.getSharedLock(STORAGE, sdUUID) File "/usr/share/vdsm/storage/task.py", line 1306, in getSharedLock self.resOwner.acquire(namespace, resName, resourceManager.LockType.shared, timeout) File "/usr/share/vdsm/storage/resourceManager.py", line 706, in acquire raise se.ResourceTimeout() ResourceTimeout: Resource timeout: () Thread-484::DEBUG::2012-10-11 10:16:49,998::task::872::TaskManager.Task::(_run) Task=`3454f584-ab39-4956-bf67-910dc0a25c27`::Task._run: 3454f584-ab39-4956-bf67-910dc0a25c27 ('dbed4cf3-a177-49a8-b41c-f12b85db4286', '11d18980-5c97-40ca-b7ff-6d1fa0f01cc8', '65f8e99b-7ee1-4020-8c23-431e3bf81242', '4f8feffd-ac58-4e4b-80b0-e50491aefb45') {} failed - stopping task