Bug 1837360
Summary: | Breakage due to updated RPM backend | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Vít Ondruch <vondruch> | ||||
Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rawhide | CC: | dwalsh, grepl.miroslav, lvrabec, mmalik, msuchy, plautrba, pmatilai, vmojzis, zpytela | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-05-27 15:28:36 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: | |||||||
Attachments: |
|
This might be just duplicate of bug 1461313, not sure AFAICS selinux-policy doesn't contain anything specific to BDB backend names, these should cover all backend formats: /var/lib/rpm(/.*)? gen_context(system_u:object_r:rpm_var_lib_t,s0) /var/lib/rpmrebuilddb.*(/.*)? gen_context(system_u:object_r:rpm_var_lib_t,s0) ...so I think its just a dupe of 1461313. It is a duplicate. See also bz#1824265 for some additional information to backend change. *** This bug has been marked as a duplicate of bug 1461313 *** |
Created attachment 1689841 [details] setroubleshoot log Description of problem: Change in RPM backend breaks SELinux and ABRT issue handling and I am not sure what else. See the attached log. Version-Release number of selected component (if applicable): $ rpm -q rpm rpm-4.15.90-0.git14971.12.fc33.x86_64 $ rpm -q setroubleshoot setroubleshoot-3.3.23-1.fc33.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: setroubleshoot spits a lot of errors into log. Expected results: setroubleshoot/ABRT works without warnings. Additional info: