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 1763868
Summary: | Existing Containers Unusable after Fedora 30 -> 31 Upgrade | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matthew Heon <mheon> |
Component: | podman | Assignee: | Matthew Heon <mheon> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 31 | CC: | awilliam, bbaude, cedric.amouyal, dustymabe, dwalsh, frantisek.kluknavsky, gmarr, jnovy, lsm5, mboddu, mheon, pasik, santiago, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | AcceptedFreezeException | ||
Fixed In Version: | podman-1.6.2 podman-1.6.2-2.fc31 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-23 18:38:40 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: | 1644940 |
Description
Matthew Heon
2019-10-21 19:15:59 UTC
Fixed in podman 1.6.2 Proposed as a Freeze Exception for 31-final by Fedora user baude using the blocker tracking app because: This impacts all silverblue upgrades from 30-31. Any containers created on 30 will not run on 31 immediately following the upgrade. This includes rootfull and rootless containers. Any systemd controlled containers that start on boot will fail unless they are recreated by the unit files on the fly as well. Error messages for the failures are not handled well in the current version of podman. podman-2:1.6.2-2 has excellent error messages and handles the migration of containers. The proper fix here is to run `podman system migrate --runtime crun` - but this flag to `podman system migrate` is only available from 1.6.2 on. +1 FE to have upgrades working smoothly ASAP. +1 FE Seems FE-worthy, especially since there is already a fix. +1FE from me. From sgallagh, per conversation on #fedora-qa: +1 FE +1 FE +1 FE That's +6, setting accepted. We need someone to attach this bug (accepted FE) to this bodhi update [1] so the update can be promoted into a RC build. [1] https://bodhi.fedoraproject.org/updates/FEDORA-2019-48a3b3e29a FEDORA-2019-48a3b3e29a has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-48a3b3e29a podman-1.6.2-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. cgroup v2 change a temporary solution options to add to the kernel sudo grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=0" shutdown -r now the container will start after to remove the option sudo grubby --update-kernel=ALL --remove-args="systemd.unified_cgroup_hierarchy=0" shutdown -r now |