Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 504144

Summary:	umount sometimes keeps keys in keyring
Product:	Red Hat Enterprise Linux 5	Reporter:	Michal Nowak <mnowak>
Component:	ecryptfs-utils	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED NOTABUG	QA Contact:	BaseOS QE <qe-baseos-auto>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.4	CC:	ohudlick
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-07-03 11:47:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Nowak 2009-06-04 13:06:58 UTC

Description of problem:

http://rhts.redhat.com/testlogs/62716/205783/1703592/TESTOUT.log

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: Testing-NOT-Key-in-Keyring
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   PASS   ] :: Unmount all sec\* dirs
2 keys in keyring:
1019058521: --alswrv     0     0 user: 6293455a29efa397
342556671: --alswrv     0     0 user: 13e8b1bc6090e91d
:: [   FAIL   ] :: Keyring is clear (Expected 0, got 1)
1
8424257
/CoreOS/ecryptfs-utils/Regression/bz501460-correct-error-msg-when-adding-to-full-keyring/Testing-NOT-Key-in-Keyring result: FAIL

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

75-5.el5.i386

How reproducible:

sometimes

Steps to Reproduce:

do ~20 times: 
   generate new SSL key
   use the new key to mount dirX
done
umount all dirs via: umount dir*/
  
Actual results:

- sometimes two keys are left in the keyring
- no error msg from umount

Expected results:

- all keys removed from keyring

Comment 1 Michal Hlavinka 2009-06-04 13:27:33 UTC

which way you mount and umount this?

Comment 2 Michal Nowak 2009-06-04 13:33:26 UTC

/sbin/mount.ecryptfs sec$keycnt/ sec$keycnt/ -o "key=openssl:openssl_keyfile=key$keycnt.pem:openssl_passwd=password,ecryptfs_cipher=des3_ede,ecryptfs_key_bytes=24,verbosity=0" &> $keycnt.out


umount sec*/

See RHTS test case: /CoreOS/ecryptfs-utils/Regression/bz501460-correct-error-msg-when-adding-to-full-keyring

Comment 3 Michal Nowak 2009-06-29 14:44:13 UTC

Is it reproducible? More info needed?

Comment 4 Michal Hlavinka 2009-07-01 06:53:02 UTC

(In reply to comment #3)
> Is it reproducible?
no, I'm not able to reproduce this at all

> More info needed?  
yes, whatever info that will help me reproduce this. How often is this reproducible for you? What platform?

Comment 5 Michal Nowak 2009-07-03 11:06:37 UTC

I don't see it happening when the test is run standalone but only when is part of test-set scheduled via RHTS web UI. The problem therefor might be that the session keyring is dirty on test start already and because of this the keyring-isClean-subtest fails.

I enhanced the test and will schedule it once more again.

Comment 6 Michal Nowak 2009-07-03 11:47:13 UTC

Ou, yee. As I said two tests were leaving keys in keyring and they should not.