Bug 1925094 - libcap-ng used by "/usr/bin/virsh" failed due to not having CAP_SETPCAP in capng_apply
Summary: libcap-ng used by "/usr/bin/virsh" failed due to not having CAP_SETPCAP in ca...
Keywords:
Status: CLOSED DUPLICATE of bug 1924218
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-04 12:01 UTC by Petr Lautrbach
Modified: 2021-02-04 12:05 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-04 12:05:42 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.