Description of problem: * single login to discover all gateways instead of issuing/executing mpath number of login commands. Currently from the initiator side we need to login to mpath number of node to get multipathed block devices at the client side. This can be minimized to single login per target by configuring all gateways for a particular target in all gateways. This bug also addresses following issues: * Redirect Configshell logs to $PATH/var/log/gluster-block/ Currently targetcli Configshell 'logfile=hello' i.e configshell logs are collected at ./hello file. Fix for this issue: Set logfile="PATH/var/log/gluster-block/gluster-block-configshell.log" * Block device creation in a non-existent/not started volume causes a silent failure. * rpcgen should be used for generating code from the block.x file It seems that rpcgen was used to generate the code for some .c and .h files at one point. But, rpcgen is not called during the build process, so changing block.x will never result in updating the generated files. Version-Release number of selected component (if applicable): 0.1.1
https://review.gluster.org/#/c/17069/ https://review.gluster.org/#/c/17059/ https://review.gluster.org/#/c/16992/ https://review.gluster.org/#/c/16897/
Merged https://review.gluster.org/#/c/17069/
Tried logging in via single node and able to discover all the gatiscsiadm -m discovery -t st -p 10.70.46.152 -l 10.70.46.152:3260,1 iqn.2016-12.org.gluster-block:e5a0be13-c41b-4c84-9e3d-215f0e5d00d5 10.70.46.144:3260,2 iqn.2016-12.org.gluster-block:b24aa6f5-ae06-4f04-8336-b922d1e8e217 10.70.46.152:3260,1 iqn.2016-12.org.gluster-block:b24aa6f5-ae06-4f04-8336-b922d1e8e217 10.70.46.144:3260,2 iqn.2016-12.org.gluster-block:de4da29e-384f-46e0-9160-d34fbb8c1f67 10.70.46.152:3260,1 iqn.2016-12.org.gluster-block:de4da29e-384f-46e0-9160-d34fbb8c1f67 10.70.46.151:3260,1 iqn.2016-12.org.gluster-block:cd6ef336-06e8-4c12-b6ee-d129e500698c 10.70.46.152:3260,2 iqn.2016-12.org.gluster-block:cd6ef336-06e8-4c12-b6ee-d129e500698c 10.70.46.144:3260,3 iqn.2016-12.org.gluster-block:cd6ef336-06e8-4c12-b6ee-d129e500698c 10.70.46.152:3260,1 iqn.2016-12.org.gluster-block:e27deff5-0c87-49e3-a2d0-84d6e8252f55 10.70.46.144:3260,2 iqn.2016-12.org.gluster-block:e27deff5-0c87-49e3-a2d0-84d6e8252f55 10.70.46.152:3260,1 iqn.2016-12.org.gluster-block:34c61c12-8694-47b9-afef-e1e9250f16a5 10.70.46.144:3260,2 iqn.2016-12.org.gluster-block:34c61c12-8694-47b9-afef-e1e9250f16a5 eways. we don't need to login to all nodes separately to discover the targets. Marking the BZ verified.gluster-block-0.2.1-1.el7rhgs.x86_64 tcmu-runner-1.2.0-4.el7rhgs.x86_64
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-2017:2773