Bug 1386149

Summary:	[ceph-iscsi-ansible]: RBD image resize not reflecting in targetcli as well as the clients
Product:	Red Hat Storage Console	Reporter:	Tejas <tchandra>
Component:	ceph-ansible	Assignee:	Paul Cuzner <pcuzner>
Status:	CLOSED ERRATA	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2	CC:	adeza, aschoen, ceph-eng-bugs, gmeno, hnallurv, kdreyer, nthomas, sankarshan
Target Milestone:	---
Target Release:	2
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	ceph-iscsi-ansible-1.3-1.el7scon ceph-iscsi-config-1.3-1.el7cp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-22 23:41:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Comment 3 Paul Cuzner 2016-10-18 22:42:11 UTC

As pointed out the resize process is working at the rbd level but targetcli is not picking this up.

The process to resolve needs the dm device to be resized for targetcli visibility - currently looking in to the best way to do this.

For the Linux client - it's straight forward;
iscsiadm -m node -R .... to rescan connections
mulitpath -ll to list the devices
pick the dm name of the device that has been resized
multipathd -k'resize map /dev/dm-X' ... to pick up the changes

Comment 4 Paul Cuzner 2016-10-19 03:49:08 UTC

Patch applied on my local repo - currently testing - should release tomorrow.

Comment 5 Paul Cuzner 2016-10-21 05:44:22 UTC

please retest with 1.3 version. multipath devices are now refreshed across gateways when an rbd is resized, allow the new size to be seen by targetcli and the client OS

Comment 6 Tejas 2016-10-25 03:19:49 UTC

Verified in version:
ceph-iscsi-ansible-1.3-1.el7scon.noarch.rpm

Comment 8 errata-xmlrpc 2016-11-22 23:41:33 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/RHBA-2016:2817