Bug 1760478
Summary: | podman 1.6 breaks the ability for RHCOS to be built | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Micah Abbott <miabbott> |
Component: | Containers | Assignee: | Lokesh Mandvekar <lsm5> |
Status: | CLOSED ERRATA | QA Contact: | weiwei jiang <wjiang> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.3.0 | CC: | aos-bugs, dwalsh, jokerman, lsm5, mheon, nagrawal |
Target Milestone: | --- | ||
Target Release: | 4.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-01-23 11:07:15 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
Micah Abbott
2019-10-10 15:52:29 UTC
Matt I think it is time to build a new vresion of podman, so that we can update the podman in rhcos. Additional testing reveals we'll likely need this PR included in the new build - https://github.com/containers/libpod/pull/4231 (In reply to Daniel Walsh from comment #1) > Matt I think it is time to build a new vresion of podman, so that we can > update the podman in rhcos. I'd prefer we wait like 5 (or 6) more days because 1.6.1-5.fc31 is just 2 days old, unless you're ok with obsoleting it. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1dd38fe32b We're going to need a fresh release to un-break Fedora 30 -> 31 upgrades, so I suspect we'll have a new release on Monday or thereabouts (In reply to Matthew Heon from comment #4) > We're going to need a fresh release to un-break Fedora 30 -> 31 upgrades, so > I suspect we'll have a new release on Monday or thereabouts Alright, SGTM. Is this still an issue? Current RHCOS 4.3 builds include podman-1.6.3-1.el8 and have been building happily. Moving to MODIFIED Verified with podman-1.6.3-1.el8.x86_64 [root@qewjosp-n4bph-master-2 /]# rpm-ostree status State: idle AutomaticUpdates: disabled Deployments: * pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1a3754d7cc780286c6803c2855ec5b2a59f6280dc403d3f23e2e28b514432cdc CustomOrigin: Managed by machine-config-operator Version: 43.81.201911200632.0 (2019-11-20T06:37:17Z) ostree://6798f144b445d33ce3e48cb31de6de8003cb364773f341e53fec3174c89a0ea0 Version: 43.81.201911192044.0 (2019-11-19T20:49:45Z) [root@qewjosp-n4bph-master-2 /]# rpm -qa|grep -i podman podman-manpages-1.6.3-1.el8.noarch podman-1.6.3-1.el8.x86_64 [root@qewjosp-n4bph-master-2 /]# rpm -ql podman-1.6.3-1.el8.x86_64 /etc/cni/net.d/87-podman-bridge.conflist /usr/bin/podman /usr/lib/.build-id /usr/lib/.build-id/47 /usr/lib/.build-id/47/2e3c686f84757a68c89c0824f50e9d0589bfe7 /usr/lib/systemd/system/io.podman.service /usr/lib/systemd/system/io.podman.socket /usr/lib/systemd/user/io.podman.service /usr/lib/systemd/user/io.podman.socket /usr/lib/tmpfiles.d/podman.conf /usr/share/bash-completion/completions/podman /usr/share/containers/libpod.conf /usr/share/doc/podman /usr/share/doc/podman/CONTRIBUTING.md /usr/share/doc/podman/README-hooks.md /usr/share/doc/podman/README.md /usr/share/doc/podman/code-of-conduct.md /usr/share/doc/podman/install.md /usr/share/doc/podman/transfer.md /usr/share/licenses/podman /usr/share/licenses/podman/LICENSE /usr/share/zsh/site-functions /usr/share/zsh/site-functions/_podman [root@qewjosp-n4bph-master-2 /]# cat /usr/lib/systemd/user/io.podman.socket [Unit] Description=Podman Remote API Socket Documentation=man:podman-varlink(1) [Socket] ListenStream=%t/podman/io.podman SocketMode=0600 [Install] WantedBy=sockets.target [root@qewjosp-n4bph-master-2 /]# systemctl --user --global preset-all [root@qewjosp-n4bph-master-2 /]# echo $? 0 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, 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:0062 |