Bug 1846213
| Summary: | os field in podman info output is empty | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Suhaas Bhat <subhat> |
| Component: | Containers | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED ERRATA | QA Contact: | weiwei jiang <wjiang> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4 | CC: | aos-bugs, dapark, dwalsh, jnovy, jokerman, mheon, ocasalsa, pmali, smccarty, tsweeney |
| Target Milestone: | --- | Keywords: | UpcomingSprint |
| Target Release: | 4.6.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | podman-1.9.3-1.rhaos4.6.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-27 16:06:32 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
Suhaas Bhat
2020-06-11 05:47:56 UTC
Matt I've assigned to you for the moment, but will ask Ashley to look at this. She is not apparently known to Bugzilla yet. We'll be shipping a Podman with that patch in 4.6, moving to post. Jindrich I think this is set for packaging, if not in your domain, please let me know. We might get this done this sprint, but definitely next. Not needed for 4.5. The PR fails to apply against podman-1.6.4 - the test part. Then it fails like this when code part of the patch is applied: # github.com/containers/libpod/cmd/podman _build/src/github.com/containers/libpod/cmd/podman/build.go:338:3: unknown field 'Architecture' in struct literal of type imagebuildah.BuildOptions _build/src/github.com/containers/libpod/cmd/podman/build.go:355:3: unknown field 'OS' in struct literal of type imagebuildah.BuildOptions error: Bad exit status from /var/tmp/rpm-tmp.Uzdob3 (%build) Seems we need to either backport to 1.6.4 or upgrade of podman to at least 1.9.3 where it is fixed. Should I update podman to 1.9.3 for rhaos-4.6? Jindrich I think updating to 1.9.3 for rhaos-4.6 sounds good to me, but I'd like Dan Walsh, Scott McCarty and Matt Heon to weigh in. The fix will definitely be in 1.9.3, and given we shipped that for 8.2.1, updating to it here SGTM I agree update to podman 1.9.3 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196 Hello, I can see that it was released for OCP 4.6, any change of being this backported to 4.5 or exists a bug for being backported to 4.5? Thanks in advance, Oscar Oscar, the bug with request for rebasing podman to 1.9.3 in RHAOS4.5 doesn't exist yet. Please file one with description why is this desired. Thanks. Hello Jindrich, I have just created BZ#1893109 for backport this to OCP 4.5. Let me know if something more is needed from my side. I was not able to define that the new bug is a clone of this Bug. Regards, Oscar podman is now updated to 1.9.3 now for both 4.4 and 4.5: 4.5: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=32659028 4.4: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=32659305 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |