Bug 1547358

Summary:	Unable to detach the disk while running commvault backup proxy.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ulhas Surse <usurse>
Component:	vdsm	Assignee:	Daniel Erez <derez>
Status:	CLOSED ERRATA	QA Contact:	Elad <ebenahar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.9	CC:	ebenahar, lsurette, lveyde, ratamir, srevivo, tnisan, ycui, ykaul, ylavi
Target Milestone:	ovirt-4.2.2	Keywords:	ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	vdsm v4.20.22	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1554289 (view as bug list)		Environment:
Last Closed:	2018-05-15 17:54:02 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:	1526197
Bug Blocks:	1554289

Description Ulhas Surse 2018-02-21 04:39:06 UTC

Description of problem:
Unable to detach the disks from the backup proxy. Though the manual detaches works. 

Version-Release number of selected component (if applicable):
RHV 4.1.9

How reproducible:
intermittent

Steps to Reproduce:
Backup proxy script tries to detach the disk and fails with following reasons as per the logs: 

 - Cannot detach Virtual Disk because the VM is in Paused status.
 - Cannot remove Virtual Disk. At least one of the VMs is not down.

Actual results:
Auto Detach of disks fails. 

Expected results:
Detach should be successful. 

Additional info:
Attaching log from commvault.

Comment 3 Allon Mureinik 2018-02-22 10:09:00 UTC

This is probably another libvirt issue (or a different facet of the same issue) around the same area.
Let's revisit once we have the original BZ fixed.

Comment 5 Elad 2018-03-16 12:19:50 UTC

[root@storage-ge6-vdsm1 ~]# repoquery --requires vdsm |grep libvirt-daemon-kvm
libvirt-daemon-kvm >= 3.2.0-14.el7_4.8

Used:
vdsm-4.20.22-1.el7ev.x86_64

Comment 10 errata-xmlrpc 2018-05-15 17:54:02 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.

https://access.redhat.com/errata/RHEA-2018:1489

Comment 11 Franta Kust 2019-05-16 13:08:30 UTC

BZ<2>Jira Resync