Bug 1643074

Summary: genconfig: set prio-path for old block volumes
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasanna Kumar Kalever <prasanna.kalever>
Component: gluster-blockAssignee: Prasanna Kumar Kalever <prasanna.kalever>
Status: CLOSED ERRATA QA Contact: RamaKasturi <knarra>
Severity: high Docs Contact:
Priority: unspecified    
Version: ocs-3.11CC: akrishna, bgoyal, kramdoss, pkarampu, pprakash, prasanna.kalever, rgeorge, rhs-bugs, sankarshan, vbellur, vinug, xiubli
Target Milestone: ---Keywords: ZStream
Target Release: OCS 3.11.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gluster-block-0.2.1-29.el7rhgs Doc Type: Bug Fix
Doc Text:
Block volumes created before load balancing feature does not have a prio_path set. With this fix, genconfig which will run automatically after the upgrade will generate prio_paths for old block volumes.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-07 03:38:29 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: 1641915, 1644154    

Description Prasanna Kumar Kalever 2018-10-25 13:13:31 UTC 
Description of problem:

old block volumes created at gluster-block before load-balancing feature got introduced won't have prio_path set. At this bz, add intelligence to genconfig, to generate true prio_paths for old blocks.
Comment 4 Rachael 2018-11-06 06:26:54 UTC 
Adding a needinfo on Prasanna based on comment 3
Comment 9 RamaKasturi 2018-11-23 13:41:06 UTC 
Verified and works fine with build 

sh-4.2# rpm -qa | grep gluster-block
gluster-block-0.2.1-29.el7rhgs.x86_64

Below are the steps followed to verify the bug:
==============================================

1) Created 5 block volumes on cns3.9 setup.

[root@dhcp46-160 ~]# heketi-cli volume info fb52bfcbc97ebf63b5e540f7da250dd9
Name: vol_fb52bfcbc97ebf63b5e540f7da250dd9
Size: 100
Volume Id: fb52bfcbc97ebf63b5e540f7da250dd9
Cluster Id: 398c9ce333452437fbcdbc8fbfac9d9b
Mount: 10.70.47.37:vol_fb52bfcbc97ebf63b5e540f7da250dd9
Mount Options: backup-volfile-servers=10.70.47.80,10.70.46.23,10.70.46.222
Block: true
Free Size: 95
Block Volumes: [3909ab5412311733406ae0b836ad1c88]
Durability Type: replicate
Distributed+Replica: 3
[root@dhcp46-160 ~]# heketi-cli blockvolume list
Id:3909ab5412311733406ae0b836ad1c88    Cluster:398c9ce333452437fbcdbc8fbfac9d9b    Name:vol-39_glusterfs_blockclaim1_0d165c58-eda7-11e8-9f94-0a580a820002
[root@dhcp46-160 ~]# oc rsh glusterfs-storage-n8dqr
sh-4.2# gluster-block info fb52bfcbc97ebf63b5e540f7da250dd9/vol-39_glusterfs_blockclaim1_0d165c58-eda7-11e8-9f94-0a580a820002
Volume fb52bfcbc97ebf63b5e540f7da250dd9 does not exist
sh-4.2# gluster-block info vol_fb52bfcbc97ebf63b5e540f7da250dd9/vol-39_glusterfs_blockclaim1_0d165c58-eda7-11e8-9f94-0a580a820002
NAME: vol-39_glusterfs_blockclaim1_0d165c58-eda7-11e8-9f94-0a580a820002
VOLUME: vol_fb52bfcbc97ebf63b5e540f7da250dd9
GBID: 00dab599-d5c0-4dc7-bf6f-3241ac3558c9
SIZE: 5368709120
HA: 3
PASSWORD: 3fd14645-2a08-4d7c-8045-d5f2a07da863
BLOCK CONFIG NODE(S): 10.70.47.37 10.70.47.80 10.70.46.23

[root@dhcp46-160 ~]# heketi-cli blockvolume list
Id:3909ab5412311733406ae0b836ad1c88    Cluster:398c9ce333452437fbcdbc8fbfac9d9b    Name:vol-39_glusterfs_blockclaim1_0d165c58-eda7-11e8-9f94-0a580a820002
Id:4afe87137f1194da227c6993d1e338c7    Cluster:398c9ce333452437fbcdbc8fbfac9d9b    Name:vol-39_glusterfs_blockclaim4_54687b22-eda8-11e8-9f94-0a580a820002
Id:8d2ef115b7591e81bf9a48657462402e    Cluster:398c9ce333452437fbcdbc8fbfac9d9b    Name:vol-39_glusterfs_blockclaim5_5eaadd88-eda8-11e8-9f94-0a580a820002
Id:b2b4752c2ea22de21c34cd9dffb6e835    Cluster:398c9ce333452437fbcdbc8fbfac9d9b    Name:vol-39_glusterfs_blockclaim3_4c1e4cbf-eda8-11e8-9f94-0a580a820002
Id:bc410b9ba803d9a96f2b6b78379c9089    Cluster:398c9ce333452437fbcdbc8fbfac9d9b    Name:vol-39_glusterfs_blockclaim2_3cf680ce-eda8-11e8-9f94-0a580a820002

2) checked if prio_path exists :
========================================
PRIOPATH does not exist in meta file :
======================================

VOLUME: vol_fb52bfcbc97ebf63b5e540f7da250dd9
GBID: 00dab599-d5c0-4dc7-bf6f-3241ac3558c9
SIZE: 5368709120
HA: 3
ENTRYCREATE: INPROGRESS
ENTRYCREATE: SUCCESS
PASSWORD: 3fd14645-2a08-4d7c-8045-d5f2a07da863
10.70.47.37: CONFIGINPROGRESS
10.70.47.80: CONFIGINPROGRESS
10.70.46.23: CONFIGINPROGRESS
10.70.47.37: CONFIGSUCCESS
10.70.47.37: AUTHENFORCED
10.70.47.80: CONFIGSUCCESS
10.70.47.80: AUTHENFORCED
10.70.46.23: CONFIGSUCCESS
10.70.46.23: AUTHENFORCED

3) upgraded the setup to 3.11.1 and verified the below:
========================================================
After upgrade to 3.11.1 i see that PRIO_PATH exists in meta file :
====================================================================
[root@dhcp46-160 block-meta]# cat vol-39_glusterfs_blockclaim1_0d165c58-eda7-11e8-9f94-0a580a820002
VOLUME: vol_fb52bfcbc97ebf63b5e540f7da250dd9
GBID: 00dab599-d5c0-4dc7-bf6f-3241ac3558c9
SIZE: 5368709120
HA: 3
ENTRYCREATE: INPROGRESS
ENTRYCREATE: SUCCESS
PASSWORD: 3fd14645-2a08-4d7c-8045-d5f2a07da863
10.70.47.37: CONFIGINPROGRESS
10.70.47.80: CONFIGINPROGRESS
10.70.46.23: CONFIGINPROGRESS
10.70.47.37: CONFIGSUCCESS
10.70.47.37: AUTHENFORCED
10.70.47.80: CONFIGSUCCESS
10.70.47.80: AUTHENFORCED
10.70.46.23: CONFIGSUCCESS
10.70.46.23: AUTHENFORCED
PRIOPATH: 10.70.47.37
[root@dhcp46-160 block-meta]# cat vol-39_glusterfs_blockclaim2_3cf680ce-eda8-11e8-9f94-0a580a820002
VOLUME: vol_fb52bfcbc97ebf63b5e540f7da250dd9
GBID: df906384-cef4-4d2d-abc2-7ab74543afc3
SIZE: 6442450944
HA: 3
ENTRYCREATE: INPROGRESS
ENTRYCREATE: SUCCESS
PASSWORD: 8edd3345-4cb2-44f1-ab6a-a856964e5331
10.70.47.37: CONFIGINPROGRESS
10.70.46.23: CONFIGINPROGRESS
10.70.47.80: CONFIGINPROGRESS
10.70.46.23: CONFIGSUCCESS
10.70.46.23: AUTHENFORCED
10.70.47.37: CONFIGSUCCESS
10.70.47.37: AUTHENFORCED
10.70.47.80: CONFIGSUCCESS
10.70.47.80: AUTHENFORCED
PRIOPATH: 10.70.46.23
[root@dhcp46-160 block-meta]# cat vol-39_glusterfs_blockclaim3_4c1e4cbf-eda8-11e8-9f94-0a580a820002
VOLUME: vol_fb52bfcbc97ebf63b5e540f7da250dd9
GBID: bc0e2585-9b6a-4179-b06b-d30ffe6ea095
SIZE: 7516192768
HA: 3
ENTRYCREATE: INPROGRESS
ENTRYCREATE: SUCCESS
PASSWORD: f89aed52-0653-4d69-bfc1-5d3edb93f862
10.70.47.37: CONFIGINPROGRESS
10.70.47.80: CONFIGINPROGRESS
10.70.46.23: CONFIGINPROGRESS
10.70.47.37: CONFIGSUCCESS
10.70.47.37: AUTHENFORCED
10.70.47.80: CONFIGSUCCESS
10.70.47.80: AUTHENFORCED
10.70.46.23: CONFIGSUCCESS
10.70.46.23: AUTHENFORCED
PRIOPATH: 10.70.47.80

[root@dhcp46-160 block-meta]# cat vol-39_glusterfs_blockclaim4_54687b22-eda8-11e8-9f94-0a580a820002
VOLUME: vol_fb52bfcbc97ebf63b5e540f7da250dd9
GBID: a97f81e6-6eb0-48d2-8c3f-820a2e2c98c9
SIZE: 4294967296
HA: 3
ENTRYCREATE: INPROGRESS
ENTRYCREATE: SUCCESS
PASSWORD: a66340da-ccad-467d-8efa-b1867f186737
10.70.47.80: CONFIGINPROGRESS
10.70.47.37: CONFIGINPROGRESS
10.70.46.23: CONFIGINPROGRESS
10.70.47.80: CONFIGSUCCESS
10.70.47.80: AUTHENFORCED
10.70.46.23: CONFIGSUCCESS
10.70.46.23: AUTHENFORCED
10.70.47.37: CONFIGSUCCESS
10.70.47.37: AUTHENFORCED
PRIOPATH: 10.70.47.80
[root@dhcp46-160 block-meta]# cat vol-39_glusterfs_blockclaim5_5eaadd88-eda8-11e8-9f94-0a580a820002
VOLUME: vol_fb52bfcbc97ebf63b5e540f7da250dd9
GBID: 94ab3b93-8dd3-4a38-8809-49dc6c895f42
SIZE: 8589934592
HA: 3
ENTRYCREATE: INPROGRESS
ENTRYCREATE: SUCCESS
PASSWORD: 68d96791-541b-4d77-8d1b-1e9feada7ec1
10.70.47.37: CONFIGINPROGRESS
10.70.46.23: CONFIGINPROGRESS
10.70.47.80: CONFIGINPROGRESS
10.70.47.37: CONFIGSUCCESS
10.70.47.37: AUTHENFORCED
10.70.46.23: CONFIGSUCCESS
10.70.46.23: AUTHENFORCED
10.70.47.80: CONFIGSUCCESS
10.70.47.80: AUTHENFORCED
PRIOPATH: 10.70.47.37


4) checked for the prio.info xattrs and this file is not present in cns3.9.

This file is present with 3.11.1 and below is what i see.

[root@dhcp46-160 block-meta]# getfattr -m. -d -e text prio.info
# file: prio.info
security.selinux="system_u:object_r:fusefs_t:s0"
user.block.10.70.46.23="1\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
user.block.10.70.47.37="2\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
user.block.10.70.47.80="2\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
Comment 10 Anjana KD 2019-01-07 08:52:22 UTC 
Updated the doc text. Kindly verify it for technical accuracy.
Comment 13 errata-xmlrpc 2019-02-07 03:38:29 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:0285