Bug 1449627

Summary:	[gluster-block] rebase rhgs-3.3 tcmu-runner to upstream tcmu-runner master
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Prasanna Kumar Kalever <prasanna.kalever>
Component:	tcmu-runner	Assignee:	Prasanna Kumar Kalever <prasanna.kalever>
Status:	CLOSED ERRATA	QA Contact:	surabhi <sbhaloth>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	amukherj, rcyriac, rhs-bugs, sbhaloth
Target Milestone:	---
Target Release:	RHGS 3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tcmu-runner-1.2.0-2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-21 04:17:54 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1417151

Description Prasanna Kumar Kalever 2017-05-10 11:40:25 UTC

Description of problem:

The recent tcmu-runner code is more stable than before, notably:

* there were lot many error handling and crash handling patches
* refactors which make made many things better
* logging improvements for better debug-ability (PRIO based) 
* lot many iSCSI commands handled
* AIO amd ALUA supported framework added which we may need in near future
* better documentation

It is much recommended that we take advantages of above listed changes. Else when the real data-path testing gets started there is a chance that we hit many of these.

Version-Release number of selected component (if applicable):
tcmu-runner-1.2.0-1.el7rhgs.x86_64.rpm

Comment 5 surabhi 2017-05-30 13:34:01 UTC

The tcmu-runner is rebased to 1.2.0 and the current available build version is tcmu-runner-1.2.0-3.el7rhgs.x86_64.

The tcmu service start,stop restarts works successfully. Moving this BZ to verified as it is for rebase, will raise bugs seperately if there are issues with tcmu-runner.

Comment 8 errata-xmlrpc 2017-09-21 04:17:54 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-2017:2773