RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1949388 - Unexpected error show in log when restarting libvirtd
Summary: Unexpected error show in log when restarting libvirtd
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: beta
: ---
Assignee: Michal Privoznik
QA Contact: yafu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-14 07:39 UTC by yafu
Modified: 2021-12-07 22:02 UTC (History)
6 users (show)

Fixed In Version: libvirt-7.5.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-07 21:57:54 UTC
Type: Bug
Target Upstream Version: 7.5.0
Embargoed:


Attachments (Terms of Use)

Description yafu 2021-04-14 07:39:28 UTC
Description of problem:
Unexpected error show in log when restarting libvirtd

Version-Release number of selected component (if applicable):
libvirt-7.0.0-4.el9.x86_64
kernel-5.11.0-2.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Restart libvirtd:
#systemctl restart libvirtd

2.Check the syslog:
#cat /var/log/messages
...
Apr 13 05:35:39 * libvirtd[189229]: libcap-ng used by "/usr/sbin/libvirtd" failed due to not having CAP_SETPCAP in capng_apply
Apr 13 05:35:39 * libvirtd[189230]: libcap-ng used by "/usr/sbin/libvirtd" failed due to not having CAP_SETPCAP in capng_apply

Actual results:
Unexpected error show in log when restarting libvirtd

Expected results:
No error show in log when restarting libvirtd


Additional info:

Comment 1 Michal Privoznik 2021-06-25 07:23:49 UTC
Patch proposed upstream:

https://listman.redhat.com/archives/libvir-list/2021-June/msg00744.html

Comment 2 Michal Privoznik 2021-06-29 06:54:35 UTC
Merged upstream as:

438b50dda8 virSetUIDGIDWithCaps: Don't drop CAP_SETPCAP right away

v7.5.0-rc1-4-g438b50dda8

Comment 5 yafu 2021-07-19 07:55:09 UTC
Verified with libvirt-daemon-7.5.0-1.el9.x86_64.

Test steps:
1.Restart libvirtd:
#systemctl restart libvirtd

2.Check the syslog:
# grep -E 'libvirtd.*fail*' /var/log/messages
no output


Note You need to log in before you can comment on or make changes to this bug.