Bug 1603207 - Capture gluster mount outputs at gluster pod startup.
Summary: Capture gluster mount outputs at gluster pod startup.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhgs-server-container
Version: cns-3.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: CNS 3.10
Assignee: Saravanakumar
QA Contact: vinutha
URL:
Whiteboard:
Depends On:
Blocks: 1568862
TreeView+ depends on / blocked
 
Reported: 2018-07-19 12:52 UTC by Humble Chirammal
Modified: 2018-09-12 10:55 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-12 10:54:03 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2688 0 None None None 2018-09-12 10:55:15 UTC

Description Humble Chirammal 2018-07-19 12:52:48 UTC
Description of problem:

At present, there the mount outputs are not captured for further debugging of the issue if there is a situation where all the mounts are not happened after container respawn. This is request for enhancing gluster container startup script with below:


    Improve a rather poor log line
    Capture all output of the mount command

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

CNS 3.10

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Humble Chirammal 2018-07-19 12:54:03 UTC
Fixed in upstream via: https://github.com/gluster/gluster-containers/pull/92/

Comment 13 errata-xmlrpc 2018-09-12 10:54:03 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:2688


Note You need to log in before you can comment on or make changes to this bug.