Bug 2032264 - avc: denied { ioctl } for pid=5170 comm="leapp3" path="/root/tmp_leapp_py3/leapp3" dev="dm-0" observed after In-place upgrading RHEL8.6 to RHEL9
Summary: avc: denied { ioctl } for pid=5170 comm="leapp3" path="/root/tmp_leapp_py3...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: leapp-repository
Version: 8.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Petr Stodulka
QA Contact: Martin Klusoň
URL:
Whiteboard:
: 2113849 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-14 09:47 UTC by Zhang Yi
Modified: 2023-08-15 08:30 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-14 07:28:20 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OAMG-6291 0 None None None 2021-12-14 09:50:57 UTC
Red Hat Issue Tracker RHELPLAN-105718 0 None None None 2021-12-14 09:50:59 UTC

Comment 1 Petr Stodulka 2021-12-14 09:55:23 UTC 
Hi Zhang, thank you for the report, we will check how to fix this later. As this is one-time issue and we are sure we will not be blocked by SELinux to execute the leapp (as the permissive mode is always expected after the upgrade) we consider this as a minor issue. But it would be nice to fix this definitely.
Comment 11 Petr Stodulka 2022-08-02 08:46:51 UTC 
*** Bug 2113849 has been marked as a duplicate of this bug. ***
Comment 16 RHEL Program Management 2023-06-14 07:28:20 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 17 Petr Stodulka 2023-06-14 07:43:16 UTC 
reopenning. it's minor problem that does not have any functional effect, but we want to address this in future.
Note You need to log in before you can comment on or make changes to this bug.