Bug 1925094

Summary:	libcap-ng used by "/usr/bin/virsh" failed due to not having CAP_SETPCAP in capng_apply
Product:	[Fedora] Fedora	Reporter:	Petr Lautrbach <plautrba>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	agedosier, berrange, clalancette, itamar, jforbes, laine, libvirt-maint, veillard, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-04 12:05:42 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:
Embargoed:

Description Petr Lautrbach 2021-02-04 12:01:16 UTC

Description of problem:

$ virsh list --all
error: failed to connect to the hypervisor
error: Failed to connect socket to '/run/user/1003/libvirt/libvirt-sock': No such file or directory


Feb 04 12:41:50 localhost.localdomain virsh[17101]: libcap-ng used by "/usr/bin/virsh" failed due to not having CAP_SETPCAP in capng_apply

Also

# systemctl status libvirtd 

reports:

Feb 04 09:36:38 localhost.localdomain libvirtd[1866]: libcap-ng used by "/usr/sbin/libvirtd" failed due to not having CAP_SETPCAP in capng_apply
Feb 04 09:36:38 localhost.localdomain libvirtd[1958]: libcap-ng used by "/usr/sbin/libvirtd" failed due to not having CAP_SETPCAP in capng_apply


Version-Release number of selected component (if applicable):
libvirt-client-7.0.0-3.fc34.x86_64
libcap-ng-0.8.2-4.fc34.x86_64

Comment 1 Daniel Berrangé 2021-02-04 12:05:42 UTC


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