Bug 1760478 - podman 1.6 breaks the ability for RHCOS to be built
Summary: podman 1.6 breaks the ability for RHCOS to be built
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.3.0
Assignee: Lokesh Mandvekar
QA Contact: weiwei jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-10 15:52 UTC by Micah Abbott
Modified: 2020-01-23 11:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-23 11:07:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:07:40 UTC

Description Micah Abbott 2019-10-10 15:52:29 UTC
When `podman-1.6.2-0.1.git589261f.el8.x86_64.rpm` landed in the RHAOS 4.3 puddle, subsequent RHCOS builds started to fail:

https://jenkins-rhcos.cloud.privileged.psi.redhat.com/job/rhcos-rhcos-4.3/64/

https://jenkins-rhcos-art.cloud.privileged.psi.redhat.com/job/rhcos-art-rhcos-4.3/128/


The root cause appears to be the same problem we saw in the Fedora CoreOS pipeline:

https://github.com/coreos/fedora-coreos-tracker/issues/290


A fix has been made upstream already, this BZ tracks the landing of the fix in `podman` downstream.

https://github.com/containers/libpod/pull/4218



Currently, RHCOS is pulling in an older version of `podman` (podman-1.4.2-5.el8.x86_64) to avoid this problem.

Comment 1 Daniel Walsh 2019-10-10 22:27:22 UTC
Matt I think it is time to build a new vresion of podman, so that we can update the podman in rhcos.

Comment 2 Micah Abbott 2019-10-11 13:34:21 UTC
Additional testing reveals we'll likely need this PR included in the new build - https://github.com/containers/libpod/pull/4231

Comment 3 Lokesh Mandvekar 2019-10-11 13:50:36 UTC
(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

Comment 4 Matthew Heon 2019-10-11 13:56:37 UTC
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

Comment 5 Lokesh Mandvekar 2019-10-11 13:59:50 UTC
(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.

Comment 6 Neelesh Agrawal 2019-11-22 18:40:58 UTC
Is this still an issue?

Comment 7 Micah Abbott 2019-11-22 20:15:12 UTC
Current RHCOS 4.3 builds include podman-1.6.3-1.el8 and have been building happily.

Moving to MODIFIED

Comment 9 weiwei jiang 2019-11-25 05:45:49 UTC
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

Comment 11 errata-xmlrpc 2020-01-23 11:07:15 UTC
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


Note You need to log in before you can comment on or make changes to this bug.