Bug 2020332
Summary: | No events reported when creating pod with --infra=false | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Katerina Koukiou <kkoukiou> |
Component: | podman | Assignee: | Charlie Doern <cdoern> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | atomic-bugs <atomic-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 9.0 | CC: | atomic-bugs, bbaude, cdoern, dwalsh, jligon, jnovy, lsm5, mheon, mmarusak, mpitt, pthomas, tsweeney, umohnani |
Target Milestone: | rc | Keywords: | Regression, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 2009296 | Environment: | |
Last Closed: | 2022-02-08 21:41:53 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: | 2009296 | ||
Bug Blocks: |
Description
Katerina Koukiou
2021-11-04 15:52:06 UTC
Assigning to Charlie who addressed the original BZ. on my machine with `podman version 4.0.0-dev` running: `curl -XPOST --unix-socket /run/user/1000/podman/podman.sock -v -H content-type:application/json http://d/v3.0.0/libpod/pods/create -d '{"name":"foo", "infra":"false"}'` followed by `curl --unix-socket /run/user/1000/podman/podman.sock http://d/v3.0.0/libpod/events?since=2m` results in an output of: `{"status":"create","id":"1a165c3232c1e2e05b5618dbb620f41efc0146507d48236e3abf7f167da1c0d3","from":"localhost/podman-pause:4.0.0-dev-1636340683","Type":"container","Action":"create","Actor":{"ID":"1a165c3232c1e2e05b5618dbb620f41efc0146507d48236e3abf7f167da1c0d3","Attributes":{"containerExitCode":"0","image":"localhost/podman-pause:4.0.0-dev-1636340683","io.buildah.version":"1.23.1","name":"edaae17ca5ce-infra"}},"scope":"local","time":1636341766,"timeNano":1636341766990067453} {"status":"create","id":"edaae17ca5ce5cf3d78172e1abee7e8b5ed72a689e0722f366d750259329c875","Type":"pod","Action":"create","Actor":{"ID":"edaae17ca5ce5cf3d78172e1abee7e8b5ed72a689e0722f366d750259329c875","Attributes":{"containerExitCode":"0","image":"","name":"foo"}},"scope":"local","time":1636341766,"timeNano":1636341766995974539}` which lists both infra and the pod being created. I am not sure how to go about resolving this, since the issue is identical just on RHEL 9. Is it possible that the version of podman is not up to date with the main branch? @Charlie: It's most probably fixed upstream already, but RHEL 9.0 currently has podman-1:3.4.2-0.2.el9.x86_64 This has been fixed upstream, tested there, and is present in Podman v4.0 which is targeted for RHEL 8.6. I'm going to close this as current release. |