Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1797531
| Summary: | Confusing error when running container with parameter --rm | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lukas Slebodnik <lslebodn> |
| Component: | podman | Assignee: | Lokesh Mandvekar <lsm5> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 32 | CC: | bbaude, debarshir, dustymabe, dwalsh, gmarr, ikavalio, jnovy, lsm5, mheon, rh.container.bot, robatino, santiago, vrothber |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | RejectedBlocker AcceptedFreezeException | ||
| Fixed In Version: | podman-1.8.2-2.fc32 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-29 00:15:27 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1705306 | ||
|
Description
Lukas Slebodnik
2020-02-03 11:21:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32. Fix is https://github.com/baude/libpod/commit/d4ce6a010b94864de31b9a1abb0654c79157b7c8 For context, see https://github.com/containers/libpod/issues/5483#issuecomment-598431764 In brief, this was a change in the Go 1.14 runtime that broke us. The fix is merged upstream, and is working its way into a release (Podman 1.8.2) that we hope to have out next week. On un-patched systems where Podman is built with Go 1.14, we expect additional error messages when containers are stopped (which will not affect exit code of the process) and (more seriously) the process in the container will be bombarded by Signal 23 at a rate of several per second on average, which could break some applications. Proposed as a Blocker for 32-final by Fedora user mheon using the blocker tracking app because: This is a serious regression in Podman caused by an upgrade of the Go toolchain to 1.14 in F32. Container processes started by `podman run` will be repeatedly sent signal 23 (several times a second) which could cause breakage in containerized applications. Fix is, fortunately, relatively simple. FEDORA-2020-92d6ffa26f has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-92d6ffa26f podman-1.8.2-2.fc32 has been pushed to the Fedora 32 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-2020-92d6ffa26f Discussed during the 2020-03-23 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker" and an "AcceptedFreezeException" was made as there are (still) no criteria at all requiring podman/container functionality to work at all so we really cannot block on this. However, it's obviously important functionality these days that we would want to work at release, so accepted as an FE issue. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-03-23/f32-blocker-review.2020-03-23-16.00.txt FEDORA-2020-92d6ffa26f has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |