Bug 1708577 - fresh install gluster pod not in 1/1 state tcmu-runner failed to find var/run/lock/tcmu.lock
Summary: fresh install gluster pod not in 1/1 state tcmu-runner failed to find var/run...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhgs-server-container
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 3.11.z Batch Update 3
Assignee: Saravanakumar
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-10 09:08 UTC by Pulkit Kundra
Modified: 2019-06-13 19:31 UTC (History)
13 users (show)

Fixed In Version: rhgs3/rhgs-server-rhel7:3.11.3-11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-13 19:18:59 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github gluster gluster-containers pull 153 0 'None' closed /var/run/lock directory is required for tcmu-runner.service 2020-02-19 08:58:05 UTC
Github open-iscsi tcmu-runner pull 550 0 'None' closed lock: create the lock directory when it is not exist 2020-02-19 08:58:05 UTC
Red Hat Product Errata RHBA-2019:1406 0 None None None 2019-06-13 19:19:09 UTC

Comment 6 Niels de Vos 2019-05-14 12:11:35 UTC 
As a workaround the directory can be created in the update-params.sh script that runs early in the container.

The right approach would be a fix in tcmu-runner, it may not rely on having /var/run/lock available and should make sure to create/provide the directories+files it needs in order to run.
Comment 13 errata-xmlrpc 2019-06-13 19:18:59 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-2019:1406
Note You need to log in before you can comment on or make changes to this bug.