Bug 761041

Summary: saslpasswd2 triggers bogus log messages ("error deleting entry from sasldb")
Product: Red Hat Enterprise Linux 6 Reporter: Stanislav Graf <sgraf>
Component: cyrus-saslAssignee: Jakub Jelen <jjelen>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: low Docs Contact:
Priority: low    
Version: 6.2CC: ebenes, pkis
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 822961 1278309 (view as bug list) Environment:
Last Closed: 2016-06-13 14:17:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 822961    

Description Stanislav Graf 2011-12-07 15:49:04 UTC
Description of problem:

Adding a new user to the SASL database ("saslpasswd2 -c username") produce error in /var/log/messages, but command is successfully executed and user exists.

# saslpasswd2 -c anyusername
Password: 
Again (for verification): 
[16:42:53] ecode=0
# tail /var/log/messages | grep 16:42
Dec  7 16:42:53 local-rhel6i saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found
Dec  7 16:42:53 local-rhel6i saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found
Dec  7 16:42:53 local-rhel6i saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found
[16:43:10] ecode=0
# sasldblistusers2
anyusername@local-rhel6i: userPassword
[16:47:50] ecode=0

Version-Release number of selected component (if applicable):
cyrus-sasl-lib-2.1.23-13.el6

How reproducible:
100%

Steps to Reproduce:
1. # saslpasswd2 -c anyusername
2. # tail /var/log/messages
3. # sasldblistusers2
  
Actual results:
Adding user produces error log

Expected results:
Adding user doesn't produce error log

Additional info:

Comment 3 Suzanne Logcher 2012-02-14 23:23:16 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 RHEL Program Management 2012-09-07 05:13:43 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2013-10-14 00:53:08 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 6 Jakub Jelen 2016-06-13 14:17:31 UTC
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6 and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.