Bug 1047333

Summary:	Deleting disk fails with glusterfs storage domain
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Sean Cohen <scohen>
Component:	vdsm	Assignee:	Nir Soffer <nsoffer>
Status:	CLOSED ERRATA	QA Contact:	Aharon Canan <acanan>
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	abaron, acathrow, amureini, bazulay, danken, iheim, knesenko, lpeer, mgoldboi, nsoffer, scohen, yeylon
Target Milestone:	---	Flags:	scohen: needinfo+
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:	vdsm-4.13.2-0.5	Doc Type:	Bug Fix
Doc Text:	getImagePath did not work on Gluster storage domains because its domain directory's base paths for Gluster domains and other file-based domains were different. Consequently, disks could not be deleted from a GlusterFS storage domain. This update uses the correct domain directories to get the images, so disks can be successfully deleted.	Story Points:	---
Clone Of:	1046600	Environment:
Last Closed:	2014-01-21 16:25:55 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:	1046600
Bug Blocks:

Description Sean Cohen 2013-12-30 12:54:55 UTC

+++ This bug was initially created as a clone of Bug #1046600 +++

Description of problem:

Deleting disk on glusterfs fails, leaving the disk in "Invalid" state. Further atempts to delete the disk fail.

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

ovirt-3.3.1

How reproducible:

Always

Steps to Reproduce:
0. Setup glusterfs storage domain
1. Create disk
2. Delete disk

Actual results:

Disk move to "Invalid state", not removed from storage.

Expected results:

Disk removed from storage.

Comment 8 Aharon Canan 2014-01-02 14:52:15 UTC

verified using vdsm-4.13.2-0.5.el6ev.x86_64.rpm (rhevh rhev-hypervisor6-6.5-20140102.0.el6ev.noarch.rpm)

Comment 9 errata-xmlrpc 2014-01-21 16:25:55 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/RHBA-2014-0040.html