Bug 1448354

Summary:	vdsmd.service fail to start because libvirt 3.2 uses GSSAPI (kerberos) instead of the insecure DIGEST-MD5 as a default mechanism
Product:	[oVirt] vdsm	Reporter:	Pei Zhang <pzhang>
Component:	General	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED DUPLICATE	QA Contact:	meital avital <mavital>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.19.12	CC:	bugs, chhu, dyuan, xuzhang, yafu, yanqzhan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-07 06:52:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pei Zhang 2017-05-05 09:26:26 UTC

Description of problem:
vdsmd.service fail to start with lasted libvirt(libvirt-3.2.0-4.el7.x86_64
), because libvirt use GSSAPI (kerberos) instead of the insecure DIGEST-MD5 as a default mechanism. Using old configuration vdsmd can start successfully.

Version-Release number of selected component (if applicable):
vdsm-4.19.12-1.el7ev.x86_64
libvirt-3.2.0-4.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install libvirt, vdsm packages
2. 
#vdsm-tool configure --force

#systemctl restart vdsmd       
Job for vdsmd.service failed because the control process exited with error code. 

3.
#vdsm-tool -vvv is-configured  
Current revision of multipath.conf detected, preserving
......
libvirt is already configured for vdsm
Modules passwd are not configured
Error:  

One of the modules is not configured to work with VDSM.
......

4. change libvirt.conf in sasl2 and use the old configuration: 

#vim /etc/sasl2/libvirt.conf
......
mech_list: DIGEST-MD5
sasldb_path: /etc/libvirt/passwd.db
......

#systemctl restart vdsmd

vdsmd service can start successfully.

Actual results:
vdsmd.service fail to start 

Expected results:
vdsmd.service can start successfully.

Additional info:

Comment 1 Yaniv Kaul 2017-05-07 06:52:53 UTC


*** This bug has been marked as a duplicate of bug 1444426 ***