Bug 1640119 - Need /var/lib/gluster-block folder bind-mounted for fix of BZ#1638988 to work
Summary: Need /var/lib/gluster-block folder bind-mounted for fix of BZ#1638988 to work
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
Assignee: Saravanakumar
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks: 1629581
TreeView+ depends on / blocked
 
Reported: 2018-10-17 11:36 UTC by Neha Berry
Modified: 2019-02-08 06:45 UTC (History)
8 users (show)

Fixed In Version: rhgs-server-container-3.11.0-5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-24 05:57:39 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2990 0 None None None 2018-10-24 05:59:07 UTC

Description Neha Berry 2018-10-17 11:36:27 UTC
Description of problem:
++++++++++++++++++++++++

See details  -https://bugzilla.redhat.com/show_bug.cgi?id=1638988#c11


As per Prasanna 

""
As of OCS-3.10 we already install a file at /var/lib/gluster-block/ called gluster-block-caps.info.

At OCS-3.11 we started maintaining the status file gb_upgrade.status at /var/lib/gluster-block/ as part of upgrade activities, and we need this directory to be persistent on pod restarts.

If we don't have /var/lib/gluster-block/ persistent, then on every pod restart, the upgrade activities will be triggered, which is not a good idea.

""

As seen, this folder is only available only on glusterfs pods, but not on the gluster-nodes. Hence the contents changed on this folder are not persistent across gluster pod restarts.


From node
===========
[root@apu-v311-app-cns-1 ~]# ls /var/lib/gluster-block
ls: cannot access /var/lib/gluster-block: No such file or directory
[root@apu-v311-app-cns-1 ~]# ls /var/lib|grep gluster
glusterd


As seen from the glusterfs pod
=================================
sh-4.2# ls -ltrh /var/log/gluster-block/
total 16K
-rw-r--r--. 1 root root  168 Oct 17 11:19 gluster-blockd.log
-rw-------. 1 root root 8.9K Oct 17 11:19 gluster-block-gfapi.log
sh-4.2# 







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

# oc describe ds glusterfs-cns |grep -i image
    Image:      ocs/rhgs-server-rhel7:v3.11
[root@apu-v311-master-0 ~]# 



How reproducible:
=====

Always

Steps to Reproduce:
1. Install OCS 3.11
2. Check for the persistence of /var/lib/gluster-block folder.

Actual results:
=======


Expected results:


Additional info:
===========

The directories currently bind-mounted to pod are
=========================

terminationMessagePolicy: File
          volumeMounts:
          - mountPath: /var/lib/heketi
            name: glusterfs-heketi
          - mountPath: /run
            name: glusterfs-run
          - mountPath: /run/lvm
            name: glusterfs-lvm
          - mountPath: /etc/glusterfs
            name: glusterfs-etc
          - mountPath: /var/log/glusterfs
            name: glusterfs-logs
          - mountPath: /var/lib/glusterd
            name: glusterfs-config
          - mountPath: /dev
            name: glusterfs-dev
          - mountPath: /var/lib/misc/glusterfsd
            name: glusterfs-misc
          - mountPath: /sys/fs/cgroup
            name: glusterfs-cgroup
            readOnly: true
          - mountPath: /etc/ssl
            name: glusterfs-ssl
            readOnly: true
          - mountPath: /usr/lib/modules
            name: kernel-modules
            readOnly: true
          - mountPath: /etc/target
            name: glusterfs-target

Comment 9 errata-xmlrpc 2018-10-24 05:57:39 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:2990


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