Bug 1823064
| Summary: | podman fails to start, selinux denials | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
| Component: | container-selinux | Assignee: | Lokesh Mandvekar <lsm5> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 32 | CC: | amurdaca, bbaude, debarshir, dwalsh, ego.cordatus, fzatlouk, gmarr, ikavalio, jchaloup, jnovy, lsm5, mheon, rh.container.bot, santiago |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | RejectedFreezeException | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-25 15:55:35 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
Miro Hrončok
2020-04-11 10:43:51 UTC
I had container-selinux-2:2.130.0-1.fc32 This is fixed via: https://bodhi.fedoraproject.org/updates/FEDORA-2020-1273245c66 container-selinux-2.131.0-1.fc32 Proposing as Fedora 32 final freeze exception. Broken podman is quite bad. Hmm, it seems I can't reproduce it. Tried in Workstation VM upgraded from F31 to F32. $ podman run -ti fedora:31 /usr/bin/bash $ echo $? 0 $ rpm -q container-selinux container-selinux-2.130.0-1.fc32.noarch $ rpm -q selinux-policy selinux-policy-3.14.5-32.fc32.noarch Discussed during the 2020-04-13 blocker review meeting: [0] The decision to classify this bug as a "RejectedFreezeException" was made as as we couldn't reproduce it. Since there's only marginal benefit to taking this as an FE versus fixing it with an update, we don't think it's worthwhile given the uncertainty. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-04-13/f32-blocker-review.2020-04-13-16.04.txt This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |