Bug 2222005
Summary: | AVC "sys_admin" pops up when rhsmcertd-worker queries a repository file it creates itself on /tmp | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Renaud Métrich <rmetrich> |
Component: | librepo | Assignee: | Jaroslav Rohel <jrohel> |
Status: | CLOSED MIGRATED | QA Contact: | swm-qe |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8.8 | CC: | ptoscano |
Target Milestone: | rc | Keywords: | MigratedToJIRA, Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-21 17:23:50 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
Renaud Métrich
2023-07-11 13:07:11 UTC
Moving to librepo, as it seems to be something done internally by librepo itself. > so probably querying the extended attributes is not that useful.
The "user.Librepo.DownloadInProgress" attribute indicates that the file is being downloaded by librepo. This xattr is removed once the file is completely downloaded. If librepo tries to resume the download, it checks if xattr is present. If not, the download will not resume, but the entire file will be downloaded again.
Strace shows that "fgetxattr" is called for this attribute. But I assume that the "fgetxattr" call will not be executed if the "resume" option is disabled.
Librepo also uses extended tributes to store the file hash. In this case, the extended attribute serves as a cache for the hash.
Sorry but there is a bug: an AVC pops up, which is not acceptable. Something has to be done to avoid it, maybe through hiding. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |