Bug 771720

Summary: libvirtd fails to start - Failed to find group record for name 'xxxxx'
Product: Red Hat Enterprise Linux 5 Reporter: Juan J. Cavallaro <jcavallaro>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.7CC: acathrow, bgollahe, bsarathy, dallan, eblake, jwest, llim, msvoboda, mzhan, pmukhedk, rwu, syeghiay, veillard, weizhan, whuang, ydu
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: libvirt-0.8.2-25.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 742646 Environment:
Last Closed: 2012-02-21 06:18:24 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:
Bug Depends On: 742646    
Bug Blocks: 743557, 782064    

Comment 7 Prasad Mukhedkar 2012-01-06 00:40:16 UTC 
Dave, 

Yes, Customer is ready to verify test build. In fact, he is eager to do that, Customer is very active if we give him test build, I'm sure he will test and reply back within a day..
Comment 8 Dave Allan 2012-01-06 00:50:07 UTC 
Awesome, DV, can you spin a test build?
Comment 9 Daniel Veillard 2012-01-06 05:01:43 UTC 
Done I have made a scratch build:

https://brewweb.devel.redhat.com/taskinfo?taskID=3922523

I have put the x86_64 packages at http://veillard.com/libvirt/5.8/
for easier access. Please provide feedback, thanks !

Daniel
Comment 10 Dave Allan 2012-01-06 16:35:12 UTC 
Prasad, let us know as soon as we have customer verification that the scratch build solves their problem.  If we get that verification by EOB Monday I think we can get the fix in 5.8.
Comment 11 Daniel Veillard 2012-01-10 01:48:40 UTC 
libvirt-0.8.2-25.el5 is built with the fix,

Daniel
Comment 17 errata-xmlrpc 2012-02-21 06:18:24 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0248.html