Bug 1878822

Summary:	Bump podman to correct version in rhos release appstream (rhos-release-rhel-8.3.repo)
Product:	Red Hat OpenStack	Reporter:	Sandeep Yadav <sandyada>
Component:	distribution	Assignee:	Lon Hohberger <lhh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jon Schlueter <jschluet>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.2 (Train)	CC:	jjoyce, jpichon, mburns, shrjoshi, wznoinsk, ykarel
Target Milestone:	---	Keywords:	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:		Environment:
Last Closed:	2020-10-01 11:52:17 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:	1879092
Bug Blocks:

Description Sandeep Yadav 2020-09-14 15:12:17 UTC

Description of problem:

Osp-16.2 need atleast need podman-1.6.4-15 in order to properly run.

But we are currently getting podman - 1.6.4-14.module+el8.3.0+7660+b7198318 from rhos release appstream(rhos-release-rhel-8.3.repo).

We need help to get correct podman version via rhos release appstream.


Fyi.. To avoid installation of wrong podman version, We have opened separate bzs to add an upper and lower constraint on podman to the rhosp-release package in 16.1 and 16.2


https://bugzilla.redhat.com/show_bug.cgi?id=1878189
https://bugzilla.redhat.com/show_bug.cgi?id=1878187

Note: this is NOT the exact same request as above bugs.


Actual results:

We are currently getting 1.6.4-14.module+el8.3.0+7660+b7198318

Expected results:

We need podman >= 1.6.4-15

Comment 1 Sandeep Yadav 2020-09-15 08:08:16 UTC

Hello Team,

Thanks to below patch -  we are now getting podman-1.6.4-20.module. 

https://code.engineering.redhat.com/gerrit/#/c/211722/
"Update Rhel 8.3 to use latest snapshot available : RHEL-8.3.0-Snapshot-3.1" 

But looks like this version is not good. Job are failing with below error:-

https://sf.hosted.upshift.rdu2.redhat.com/logs/43/211643/2/check/periodic-tripleo-ci-rhel-8-scenario001-standalone-cinder-rhos-16.2/b71ad62/logs/undercloud/home/zuul/standalone_deploy.log
~~~
time="2020-09-15T06:52:04Z" level=error msg="Error forwarding signal 23 to container b3792982b3938f19e62bfdc00b4405a4f073ac32e150c1745c251211e3618b7c: container has already been removed"
time="2020-09-15T06:52:04Z" level=error msg="Error forwarding signal 23 to container b3792982b3938f19e62bfdc00b4405a4f073ac32e150c1745c251211e3618b7c: container has already been removed"
~~~

Checking with pidone folks - we came to know about bug:

"podman run with --rm errors out/segfaults in container-tools-2.0-8.3.0"
https://bugzilla.redhat.com/show_bug.cgi?id=1875289

Fix is present in podman-1.6.4-21.module+el8.3.0+7994+3dff63cb.x86_64. We need atleast podman-1.6.4-21.

Comment 2 Lon Hohberger 2020-09-15 16:53:57 UTC

Unfortunately, podman-1.6.4-21 is missing the fixes for these two bugzillas (regression from 8.2.0):

https://bugzilla.redhat.com/show_bug.cgi?id=1846364
https://bugzilla.redhat.com/show_bug.cgi?id=1834346

So, 1.6.4-21 may be okay for testing for the moment, but it is likely we will need to await further fixes.