Bug 1329405

Summary:	vdsm configures digest-md5 auth, but does not require cyrus-sasl-md5
Product:	[oVirt] vdsm	Reporter:	Pat Riehecky <riehecky>
Component:	Packaging.rpm	Assignee:	Yaniv Bronhaim <ybronhei>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Aharon Canan <acanan>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.17.23.1	CC:	bugs, riehecky
Target Milestone:	ovirt-4.0.0-beta	Flags:	ybronhei: ovirt-4.0.0? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-04 08:07:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Pat Riehecky 2016-04-21 20:24:35 UTC

Description of problem:
When vdsm is setting up its runtime environment is configures use of SASL's digest-md5.  However, it does not require cyrus-sasl-md5 be installed.

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


How reproducible:vdsm-4.17.23.2-0.el7.centos.noarch


Steps to Reproduce:
1. install very very minimal RHEL7.2 system
2. install vdsm
3. attempt to start vdsm

Actual results:
sasldblistusers2[3143]: _sasldb_getkeyhandle has failed
sasldblistusers2[3143]: DIGEST-MD5 common mech free


Expected results:
No errors

Additional info:

Comment 1 Yaniv Bronhaim 2016-04-24 12:48:12 UTC

you should see an error in /var/log/messages. can you attach that file? "vdsm-tool configure --module passwd" uses sasl to set libvirt password . you can try to rerun it if the failure indeed exists. then attach the output please.

Comment 2 Pat Riehecky 2016-04-25 13:37:41 UTC

The host I was using has been rolled into production.  I'll see about building up an additional system for replication.

preserving needinfo until I actually do the task.

Comment 3 Sandro Bonazzola 2016-05-02 10:03:00 UTC

Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 4 Yaniv Bronhaim 2016-05-04 08:07:01 UTC

Please attach relevant logs and re-open if the issue is indeed exist. till then closing with INSUFFICIENT_DATA