Bug 1402334

Summary: Getting the warning message while erasing the gluster "glusterfs-server" package.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Byreddy <bsrirama>
Component: glusterfindAssignee: Milind Changire <mchangir>
Status: CLOSED ERRATA QA Contact: Vinayak Papnoi <vpapnoi>
Severity: high Docs Contact:
Priority: medium    
Version: rhgs-3.2CC: amukherj, apaladug, mchangir, rcyriac, rhs-bugs, sanandpa, sankarshan, sheggodu, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.4.z Batch Update 2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.12.2-27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1402369 (view as bug list) Environment:
Last Closed: 2018-12-17 17:07:02 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: 1402369, 1402671    
Bug Blocks:    

Description Byreddy 2016-12-07 09:38:29 UTC 
Description of problem:
========================
Getting the warning message while erasing the gluster packages.

 Erasing    : glusterfs-server-3.8.4-7.el7rhgs.x86_64                                                                                                                                   8/17 
warning: file /var/lib/glusterd/glusterfind/.keys: remove failed: No such file or directory
success
  Erasing    : glusterfs-fuse-3.8.4-7.el7rhgs.x86_64    


Note: This issue is not there in rhgs 3.1.3 build (more details in additional  info section)


Version-Release number of selected component (if applicable):
=============================================================
glusterfs-server-3.8.4-7.el7rhgs.x86_64   

How reproducible:
=================
Always

Steps to Reproduce:
===================
1. Install the above mentioned build 
2. Create -> start -> stop -> delete a simple volume.
3. Try to erase the packages, you will see the above warning message.

Actual results:
==============
Getting the warning message while erasing the gluster packages.


Expected results:
=================
No warning message should come

Additional info:
================
problem in 3.2 is, the ".key"  file is not creating in 3.2 after installation of bits  BUT the same file is present in 3.1.3 build after installation.
Comment 2 Atin Mukherjee 2016-12-07 09:46:26 UTC 
Is there any functional impact here apart from the log? I guess no right?
Comment 3 Byreddy 2016-12-07 09:53:04 UTC 
(In reply to Atin Mukherjee from comment #2)
> Is there any functional impact here apart from the log? I guess no right?

No functionality loss BUT
This is Regression and TPS package erase tests will fail.
Comment 4 Milind Changire 2016-12-07 11:50:30 UTC 
I think would be functional impact here.

gluster volume delete causes the "post delete" hook script to run. The "post delete" script mistakenly deletes the .keys directory under /var/lib/glusterd/glusterfind which may cause SSH keys to be deleted if there were glusterfind sessions created on the node.

Although the issue has become evident as part of erasing RPMs, the problem is not related to packaging.

This needs to be fixed.
Comment 5 Byreddy 2016-12-07 12:48:59 UTC 
(In reply to Milind Changire from comment #4)
> I think would be functional impact here.
> 
> gluster volume delete causes the "post delete" hook script to run. The "post
> delete" script mistakenly deletes the .keys directory under
> /var/lib/glusterd/glusterfind which may cause SSH keys to be deleted if
> there were glusterfind sessions created on the node.
> 
> Although the issue has become evident as part of erasing RPMs, the problem
> is not related to packaging.
> 
> This needs to be fixed.

Thanks a lot for your update Milind
Comment 6 Atin Mukherjee 2016-12-07 13:59:59 UTC 
upstream mainline patch http://review.gluster.org/#/c/16052 posted for review.
Comment 24 errata-xmlrpc 2018-12-17 17:07:02 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:3827