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.

Bug 700442

Summary: There are createVolume/copyImage tasks that stuck in "running" status
Product: Red Hat Enterprise Linux 6 Reporter: Rami Vaknin <rvaknin>
Component: vdsmAssignee: Saggi Mizrahi <smizrahi>
Status: CLOSED ERRATA QA Contact: Kiril Nesenko <knesenko>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: abaron, bazulay, danken, dfediuck, iheim, ilvovsky, mgoldboi, sgrinber, yeylon, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: vdsm-4.9-66.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 07:15:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 705815    
Bug Blocks:    
Attachments:
Description Flags
Logs
none
log none

Description Rami Vaknin 2011-04-28 12:36:27 UTC
Created attachment 495525 [details]
Logs

Environment: RHEVM 2.3 on dev env, RHEL 6.1 host, vdsm-4.9-62.el6.x86_64

These tasks run the dd command and remain stuck in "running" status, it occurred during automation testing which create vm with 8 disks and 8 nics and make a template+pool+5 pool's VMs from that template.

[root@intg-vdsb ~]# vdsClient -s 0 getAllTasksStatuses 
{'status': {'message': 'OK', 'code': 0}, 'allTasksStatus': {'ebeeb83d-94b7-4dfc-8bc2-2e3dd41b042a': {'message': '1 jobs completed successfuly', 'code': 0, 'taskID': 'ebeeb83d-94b7-4dfc-8bc2-2e3dd41b042a', 'taskResult': 'success', 'taskState': 'finished'}, '4b7beb90-b043-478d-9d61-31ff1aed3416': {'message': 'Task is initializing', 'code': 0, 'taskID': '4b7beb90-b043-478d-9d61-31ff1aed3416', 'taskResult': '', 'taskState': 'running'}, 'b686b60c-49bd-4983-a8de-a011ff20e8cf': {'message': '1 jobs completed successfuly', 'code': 0, 'taskID': 'b686b60c-49bd-4983-a8de-a011ff20e8cf', 'taskResult': 'success', 'taskState': 'finished'}, 'eec70dfb-042d-482a-b235-356578ec5383': {'message': '1 jobs completed successfuly', 'code': 0, 'taskID': 'eec70dfb-042d-482a-b235-356578ec5383', 'taskResult': 'success', 'taskState': 'finished'}, 'ca3bef4c-0cee-49f7-a78c-5a21fe7ac17d': {'message': '1 jobs completed successfuly', 'code': 0, 'taskID': 'ca3bef4c-0cee-49f7-a78c-5a21fe7ac17d', 'taskResult': 'success', 'taskState': 'finished'}, '883f31db-076b-49f2-8c93-96516289a824': {'message': 'Task is initializing', 'code': 0, 'taskID': '883f31db-076b-49f2-8c93-96516289a824', 'taskResult': '', 'taskState': 'running'}, '92df454a-7068-4e41-b5e1-d51e189600a2': {'message': '1 jobs completed successfuly', 'code': 0, 'taskID': '92df454a-7068-4e41-b5e1-d51e189600a2', 'taskResult': 'success', 'taskState': 'finished'}, '045d34d0-c57e-4f6a-a578-045a99a26413': {'message': '1 jobs completed successfuly', 'code': 0, 'taskID': '045d34d0-c57e-4f6a-a578-045a99a26413', 'taskResult': 'success', 'taskState': 'finished'}}}

[root@intg-vdsb ~]# vdsClient -s 0 getAllTasksInfo 
ebeeb83d-94b7-4dfc-8bc2-2e3dd41b042a :
	verb = createVolume
	id = ebeeb83d-94b7-4dfc-8bc2-2e3dd41b042a
4b7beb90-b043-478d-9d61-31ff1aed3416 :
	verb = createVolume
	id = 4b7beb90-b043-478d-9d61-31ff1aed3416
b686b60c-49bd-4983-a8de-a011ff20e8cf :
	verb = createVolume
	id = b686b60c-49bd-4983-a8de-a011ff20e8cf
eec70dfb-042d-482a-b235-356578ec5383 :
	verb = createVolume
	id = eec70dfb-042d-482a-b235-356578ec5383
ca3bef4c-0cee-49f7-a78c-5a21fe7ac17d :
	verb = createVolume
	id = ca3bef4c-0cee-49f7-a78c-5a21fe7ac17d
883f31db-076b-49f2-8c93-96516289a824 :
	verb = createVolume
	id = 883f31db-076b-49f2-8c93-96516289a824
92df454a-7068-4e41-b5e1-d51e189600a2 :
	verb = createVolume
	id = 92df454a-7068-4e41-b5e1-d51e189600a2
045d34d0-c57e-4f6a-a578-045a99a26413 :
	verb = createVolume
	id = 045d34d0-c57e-4f6a-a578-045a99a26413

[root@intg-vdsb ~]#

Comment 2 Dafna Ron 2011-04-28 12:45:27 UTC
Created attachment 495528 [details]
log

I had the same thing happen in vdsm 59
I started VM with 11 disks in stateless and the VM got stuck on image locked. 
looking at the tasks, I could see that there were 2 tasks that were still running even though the snapshots for each disk appeared to have finished. 

I have attached the vdsm log from yesterday.

Comment 3 Saggi Mizrahi 2011-05-02 13:02:57 UTC
http://gerrit.usersys.redhat.com/338

Comment 5 Kiril Nesenko 2011-05-24 10:06:36 UTC
Blocked by 705815

Comment 6 Kiril Nesenko 2011-05-30 06:32:16 UTC
Verified
ic119

Comment 7 errata-xmlrpc 2011-12-06 07:15:23 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/RHEA-2011-1782.html