Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1557830

Summary: memory leakage when doing the alua implicit transition
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: liuwei <wliu>
Component: iSCSIAssignee: Mike Christie <mchristi>
Status: CLOSED ERRATA QA Contact: Madhavi Kasturi <mkasturi>
Severity: medium Docs Contact: Aron Gunn <agunn>
Priority: medium    
Version: 3.0CC: agunn, ceph-eng-bugs, ceph-qe-bugs, jbiao, jdillama, jiajzhan, mchristi, mhackett, mkasturi, peli, tchandra
Target Milestone: z3   
Target Release: 3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: tcmu-runner-1.3.0-0.4.1.el7cp Doc Type: Bug Fix
Doc Text:
.Fixed a memory leak when doing an Asymmetric Logical Unit Assignment (ALUA) implicit transition When the `tcmu-runner` does a failover, a new thread is created. This new thread takes the device's lock. The `tcmu-runner` was not cleaning up the thread after the failover operation was finished. This resulted in a memory leak and failovers would fail, because the subsequent new threads could not be created. In this release, the new thread is created in a detached state, allowing successful cleanup automatically once the failover process has completed.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-15 18:20:31 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:

Description liuwei 2018-03-19 02:11:14 UTC 
Description of problem:

Due to below error,  the client (Vmware) can't access the iscsi target volume stable.


Mar 14 09:20:32 osd10 tcmu-runner: 2018-03-14 09:20:32.007 2312 [ERROR] alua_implicit_transition:461 rbd/rbd.gw2lun013: Could not start implicit transition thread:Cannot allocate memory
Mar 14 09:20:32 osd10 tcmu-runner: 2018-03-14 09:20:32.007 2312 [ERROR] alua_implicit_transition:461 rbd/rbd.gw2lun017: Could not start implicit transition thread:Cannot allocate memory
Mar 14 09:20:32 osd10 tcmu-runner: 2018-03-14 09:20:32.011 2312 [ERROR] alua_implicit_transition:461 rbd/rbd.gw2lun024: Could not start implicit transition thread:Cannot allocate memory



From the upstream site. I found the patch which has been fixed. So, Please backport it to our rpm version.


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

cat installed-rpms | grep ceph
ceph-base-12.2.1-40.el7cp.x86_64                            Mon Dec 25 01:45:02 2017
ceph-common-12.2.1-40.el7cp.x86_64                          Mon Dec 25 01:44:19 2017
ceph-iscsi-cli-2.5-9.el7cp.noarch                           Mon Dec 25 22:31:05 2017
ceph-iscsi-config-2.3-12.el7cp.noarch                       Mon Dec 25 08:49:28 2017
ceph-iscsi-tools-2.1-3.el7cp.noarch                         Mon Dec 25 22:54:29 2017
ceph-osd-12.2.1-40.el7cp.x86_64                             Mon Dec 25 01:45:23 2017
ceph-selinux-12.2.1-40.el7cp.x86_64                         Mon Dec 25 01:45:02 2017
libcephfs2-12.2.1-40.el7cp.x86_64                           Mon Dec 25 01:44:16 2017
python-cephfs-12.2.1-40.el7cp.x86_64                        Mon Dec 25 01:44:16 2017

cat installed-rpms | grep tcmu
libtcmu-1.3.0-0.4.el7cp.x86_64                              Mon Dec 25 08:49:31 2017
tcmu-runner-1.3.0-0.4.el7cp.x86_64                          Mon Dec 25 08:49:31 2017


Kernel Version:

cat uname 
Linux osd1.zyc4.cmicnmg.com 3.10.0-858.el7.x86_64 #1 SMP Tue Feb 27 08:59:23 EST 2018 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:

100%reproduced 


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


fix it ASAP

Additional info:
Comment 4 Mike Christie 2018-03-19 03:12:43 UTC 
This will be fixed in RHCS 3.1 and the next RHCS 3.0 z stream as we will be syncing runner to upstream to bring in the new explicit failover support.
Comment 77 errata-xmlrpc 2018-05-15 18:20:31 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-2018:1563