Bug 763988 (GLUSTER-2256)

Summary:	openssl fails
Product:	[Community] GlusterFS	Reporter:	Saurabh <saurabh>
Component:	distribute	Assignee:	Raghavendra G <raghavendra>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.1.1	CC:	gluster-bugs, vijay
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	nfs
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Saurabh 2010-12-28 12:15:03 UTC

Openssl script fails both on nfs and fuse mount on cleints,
whereas it is a pass if the script is executed over ths nfs mount on the server on which the volume resides,

Failure logs on nfs mount can be accessed from the machine 192.168.1.190
from file /mnt/logs/open28decnfs.log
and for fuse mount can be accessed from same machine from file /mnt/logs/open.log

and infact when I am executing the open.sh over fuse mount(client as 3.1.1) from my laptop the error is different. I am attaching the logs from my laptop with this bug.

Pass logs are residing on the machine 192.168.1.91 in file 
/mnt/logs/open28decnfs.log 

login credentials for 192.168.1.190 is gluster:gluster, presently I am using it as client for testing, requesting to use it only for viewing the logs.

Comment 1 Saurabh 2011-01-04 07:24:35 UTC

presently I had dowloaded a latest tarball of openssl from net and tried to install it and it went fine over nfs mount.

I will try the same for glusterfs mount.


Earlier, i had to reproduce the issue again using the script open.sh and manually using the existing tarball from central repository and it was similar errors as mentioned in bug earlier.

Hence considerring this may be a issue with script or with the tarball.

Comment 2 Raghavendra G 2011-01-10 01:36:58 UTC

Saurabh,

Can we mark this bug as fixed, since you are not finding the issue with latest openssl tarball? Also, can you check whether build of older openssl version (which had problems on glusterfs) had similar issues on backend file system?

regards,
Raghavendra.

Comment 3 Saurabh 2011-01-11 03:35:57 UTC

Yeah, with the new tarball there was no issue.
with the older tarball I didn't try to install just on linux, as i was trying to finish of other things.