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 2123371 - [libvirt] Kernel does not provide mount namespace [rhel-9.2.0]
Summary: [libvirt] Kernel does not provide mount namespace [rhel-9.2.0]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Michal Privoznik
QA Contact: yalzhang@redhat.com
URL:
Whiteboard:
Depends On: 2121141
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-01 13:44 UTC by RHEL Program Management Team
Modified: 2023-05-09 08:08 UTC (History)
9 users (show)

Fixed In Version: libvirt-8.7.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2121141
Environment:
Last Closed: 2023-05-09 07:27:05 UTC
Type: ---
Target Upstream Version: 8.7.0
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-133012 0 None None None 2022-09-01 13:45:00 UTC
Red Hat Product Errata RHBA-2023:2171 0 None None None 2023-05-09 07:27:29 UTC

Comment 1 Jiri Denemark 2022-09-01 13:53:01 UTC 
Fixed upstream by

commit 589536e75d2af745c8f27134b466b23e4fbe3e95
Refs: v8.6.0-48-g589536e75d
Author:     Michal Prívozník <mprivozn>
AuthorDate: Wed Aug 3 12:27:19 2022 +0200
Commit:     Michal Prívozník <mprivozn>
CommitDate: Thu Aug 4 15:33:11 2022 +0200

    qemu_process: Destroy domain's namespace after killing QEMU

    After QEMU is killed in qemuProcessStop() its mount namespace
    doesn't exist anymore, because it was the only process running
    there. Thus we should clear our internal flag that the domain has
    namespace enabled so that seclabel restore code does not try to
    enter it. We do the same in qemuProcessHandleMonitorEOF() but
    when it is us, who decides to kill QEMU rather than QEMU quitting
    we haven't seen EOF by the time qemuProcessStop() is called.

    Signed-off-by: Michal Privoznik <mprivozn>
    Reviewed-by: Martin Kletzander <mkletzan>
Comment 2 yalzhang@redhat.com 2022-09-22 09:26:14 UTC 
Reproduce on libvirt-8.5.0-5.el9.x86_64, and can not reproduce on libvirt-8.7.0-1.el9.x86_64 with the same steps in bug 2121141#c11.
Comment 5 yalzhang@redhat.com 2022-09-27 09:48:42 UTC 
verified per comment 2.
Comment 7 errata-xmlrpc 2023-05-09 07:27:05 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 (libvirt bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2023:2171
Note You need to log in before you can comment on or make changes to this bug.