Bug 1031029

Summary: Exit message: internal error unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified
Product: Red Hat Enterprise Linux 6 Reporter: Michael Everette <meverett>
Component: libvirtAssignee: Jiri Denemark <jdenemar>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.4CC: acathrow, ajia, benglish, bili, dyuan, jdenemar, lsu, meverett, mzhan
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-10 21:00:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Comment 3 Jiri Denemark 2013-12-05 17:43:56 UTC
It looks like the XML libvirt got from vdsm was wrong. Vdsm turns off automatic disk leases and so it is supposed to explicitly configure leases for all read/write disks used by a domain. The "Read/write, exclusive access, disks were present, but no leases specified" error is reported when there are read/write disks attached to a domain but there are no leases configured for them. Can you get the XML vdsm uses for the domain?

Comment 4 Jiri Denemark 2013-12-05 17:48:07 UTC
I talked to Federico from RHEV storage team and apparently vdsm is configuring libvirt (in /etc/libvirt/qemu-sanlock.conf) so that

auto_disk_leases = 0
require_lease_for_disks = 0

However, the reported error message should only be reported if

auto_disk_leases = 0
require_lease_for_disks = 1

and there are no leases in domain XML.

That said, this looks like someone changed require_lease_for_disks to 1. Michael, can you check if that's the case?

Comment 5 Michael Everette 2013-12-05 17:52:24 UTC
I will ask customer for it now.

Comment 6 Michael Everette 2013-12-10 14:47:37 UTC
Customer has closed the case and not provided the info requested. He has updated to the latest iso and says he does not see same behaviour. We can close this bug. Thank you for the help.

Comment 7 Jiri Denemark 2013-12-10 21:00:43 UTC
Thanks, I assume the problem was in wrong configuration of libvirt and whatever caused it is now gone.