Bug 1958546
| Summary: | 3.2.0-rc1 opening file `` for writing: No such file or directory: OCI not found | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Guy Streeter <guy.streeter> | ||||
| Component: | podman | Assignee: | Lokesh Mandvekar <lsm5> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 34 | CC: | acui, adam, bbaude, container-sig, debarshir, dwalsh, james, jnovy, lsm5, mheon, mschmidt, patrick, pehunt, redhat, rh.container.bot, robinlee.sysu, sanjay.ankur, santiago, tino.wolf.1980 | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-03-23 13:35:01 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: |
|
||||||
I removed my containers and images and rebuilt my pod, and I'm no longer getting the error. I met the same error with podman-3.2.0-0.1.rc1.fc34.x86_64 Containers that created by toolbox-0.0.99.1-1.fc34.x86_64 with the previous podman-3.1.2-1.fc34.x86_64 fails to start. Re-created containers would run, with the same version of Toolbox. Fixed upstream. The real issue here is that an early RC somehow made it into the stable repos. We are taking action to back out the the RC and restore 3.1.2 to stable until the final 3.2.0 release. Hi Matthew, Thanks for this. Would it be possible to not use the bot for stable releases, as noted by pnemade in the update? Bodhi already includes the necessary logic that the update process should follow as documented by FESCo, and this should only be overridden by a human if necessary, not by a bot. https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#stable-releases etc. I also note that the version in rawhide appears to be older than the version in F33/34 (3.1.0... vs 3.2.0) because the bot keeps obsoleting updates in rawhide? Could the tooling please be tweaked to ensure that the rawhide version does always remain ahead of stable Fedora releases (perhaps by not obsoleting each update until it has actually made it to "stable" there)? https://bodhi.fedoraproject.org/updates/?packages=podman Thanks very much, I'm not really the correct target for these questions - I'll tag in Lokesh, who manages the Podman package for Fedora. The same happens to me on my headless Fedora 33 Server-Edition. Rolling back to version 3.1.0 is running fine. Does this still occur with v3.2.3 in updates or with v3.3.0-rc1 (soon to land in f34-updates-testing)? Closing. Please reopen if you still notice this issue with v4.0.2. |
Created attachment 1781074 [details] podman pod inspect output. Description of problem: After upgrading podman to 3.2.0-rc1, I get: opening file `` for writing: No such file or directory: OCI not found failure for all my pods. Downgrading to 3.1.0 the problem goes away. Version-Release number of selected component (if applicable): 3.2.0-rc1 How reproducible: This happens every time I try to start any of my pods with the new version. It never happens with version 3.1.0. Actual results: error starting container ede27395508dc8dc8485829b9f8d65384bbc5a1666b4d589252b67b20c76841a: opening file `` for writing: No such file or directory: OCI not found Expected results: Successful start of pod. Additional info: I only have rootless pods, so I have not tried anything as root and I have not tried single containers.