Bug 1564084

Summary: [tcmu-runner] tcmu_rbd_lock_break and tcmu_notify_lock_lost errors on reboot of gw node
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Madhavi Kasturi <mkasturi>
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, edonnell, jbrier, jdillama, kdreyer, mchristi, tchandra, vereddy
Target Milestone: rc   
Target Release: 3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tcmu-runner-1.4.0-0.1.el7cp Doc Type: Bug Fix
Doc Text:
.Rebooting the Object Gateway no longer sees the `tcmu_rbd_lock_break` and `tcmu_notify_lock_lost` errors During failover/failback and initial device discovery with a multipath setup, `tcmu-runner` may need to take the lock away from another iSCSI gateway. When this happens the initiator may be sending IO to multiple paths at the same time, so multiple gateways will try to take the lock from each other. This can result in errors like: `Could not break lock from $locker_id (Err -16)` These errors are expected temporarily while the failover/failback or device setup process is executing. However, `tcmu-runner` would sometimes not fully clean itself up after losing the lock, so the `-16` error would repeat and the gateway could not be used until it was rebooted. The `tcmu-runner` daemon has been changed to always reopen the device after losing the lock so the internal state is reinitialized before use. With this update to {product}, failover/failback and device set up complete. Lock breaking errors with the error code `-16` should only temporarily be logged to the target logs.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-26 18:19:46 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: 1557269    

Comment 25 errata-xmlrpc 2018-09-26 18:19:46 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:2819