Bug 1756972
Summary: | building Fedora 31 packages on Fedora 30 cause SELinux contexts to be unmapped | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sjoerd Mullender <sjoerd> |
Component: | mock | Assignee: | Miroslav Suchý <msuchy> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 30 | CC: | amessina, ego.cordatus, jdisnard, jkeating, markus.linnala, mebrown, mhroncok, msuchy, philip.wyett, praiskup, umar, vascom2, vitaly, williams |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | mock-1.4.21-1.fc31 mock-1.4.21-1.fc30 mock-1.4.21-1.fc29 mock-1.4.21-1.el8 mock-1.4.21-1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-05 04:15:14 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
Sjoerd Mullender
2019-09-30 10:57:04 UTC
Can you please check this happens also with mock v1.4.20? I'm afraid it does: Oct 08 13:16:21 localhost.localdomain kernel: SELinux: Converting 2421 SID table entries... Oct 08 13:16:21 localhost.localdomain kernel: SELinux: Context system_u:object_r:plymouthd_var_lib_t:s0 became invalid (unmapped). Oct 08 13:16:21 localhost.localdomain kernel: SELinux: Context system_u:object_r:plymouthd_var_run_t:s0 became invalid (unmapped). Oct 08 13:16:21 localhost.localdomain kernel: SELinux: Context system_u:object_r:nfsd_exec_t:s0 became invalid (unmapped). [...] rpm -q mock says mock-1.4.20-1.fc30.noarch. Hmm, this just worked fine on my F30 box, even with mock v1.4.19. Can you please provide your configuration? Is there something specific on your host? It even fails in a VM. My desktop is XFCE. Using libvirt and the Virtual Machine Manager entry in the menu I create a Fedora 30 instance (again XFCE), run it, install mock and then run the command in the Steps to Reproduce. It doesn't matter if I first do "sudo usermod -a -G mock $USER" and login again (to be a member of the mock group). Just to be sure, I just create a new VM using the Fedora-Everything-netinst-x86_64-30-1.2.iso image I had lying around. Installed using the defaults mostly, except using English and installing the XFCE desktop. After it came up, I logged in, ran "sudo dnf upgrade -y" (didn't do anything remotely relevant), then installed mock from updates-testing and tested. Testing consisted of running the mock command (copy+paste from this bug report) in one window and running "journalctl -f" in another. When the selinux-policy-minimum scriptlet was getting executed, journalctl started spewing the quoted messages. Ah, I was doing it wrong. Thanks for your patience, indeed reproducible. Can you please try this, and provide feedback? ``` dnf copr enable praiskup/mock-fixes dnf update mock ``` Once this finishes: https://copr.fedorainfracloud.org/coprs/praiskup/mock-fixes/build/1051569/ You need mock-1.4.20-1.git.5.fe9bfeb.fc31. Pull request (you can build on your own): https://github.com/rpm-software-management/mock/pull/371 Seems to work. No more nasty SELinux messages when the RPMs get installed. I used mock-1.4.20-1.git.5.fe9bfeb.fc30.noarch (not fc31) since this was on a Fedora 30 VM, but of course installing the Fedora 31 environment. Thank you for confirmation. *** Bug 1761201 has been marked as a duplicate of this bug. *** This issue is pretty serious; I'd vote for new mock release to get this fixed. *** Bug 1754807 has been marked as a duplicate of this bug. *** *** Bug 1767097 has been marked as a duplicate of this bug. *** The recipe given in bug 1767097 solved that problem for me. This was for using mock on fc31 to build fc31 packages. Are we sure these are the same issues? I protest, #1767097 does not seem to be duplicate of this issue, more explanation at: https://bugzilla.redhat.com/show_bug.cgi?id=1767097#c5 I am pretty sure it is the same. See https://bugzilla.redhat.com/show_bug.cgi?id=1754807#c10 for the same symptomps. You can check nightly builds https://copr.fedorainfracloud.org/coprs/g/mock/mock/ if it fix your issue. FEDORA-2019-c6079af90e has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c6079af90e FEDORA-2019-ad7ecf205b has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ad7ecf205b FEDORA-EPEL-2019-0549ec172d has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0549ec172d FEDORA-EPEL-2019-3687ce895a has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-3687ce895a FEDORA-2019-755583cbdf has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-755583cbdf mock-1.4.21-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c6079af90e mock-1.4.21-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0549ec172d mock-1.4.21-1.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-3687ce895a mock-1.4.21-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ad7ecf205b mock-1.4.21-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-755583cbdf mock-1.4.21-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. mock-1.4.21-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. mock-1.4.21-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. mock-1.4.21-1.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report. mock-1.4.21-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. |