Bug 1861777

Summary:	We must have an upper and minor version limit for podman package
Product:	Red Hat OpenStack	Reporter:	Cédric Jeanneret <cjeanner>
Component:	rhosp-director	Assignee:	Lon Hohberger <lhh>
Status:	CLOSED DUPLICATE	QA Contact:	David Rosenfeld <drosenfe>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	16.1 (Train)	CC:	jjoyce, jpichon, kchamart, mburns, morazi
Target Milestone:	z2	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
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:	2022-01-13 10:33:05 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 Cédric Jeanneret 2020-07-29 14:16:41 UTC

Description of problem:
It might happen operator doesn't have the right repositories enabled, and it might lead to a wrong version of podman being pulled in.

This is shown for instance here:
https://bugzilla.redhat.com/show_bug.cgi?id=1860640

An idea would be to set that upper limit against paunch package, since it's installed everywhere (for now).

The version should prevent to install any other version than podman-1.6.4*

Cheers,

C.

Comment 1 Cédric Jeanneret 2020-07-30 08:59:59 UTC

Seems something has been corrected in the meantime, but having this security net wouldn't hurt:
https://bugzilla.redhat.com/show_bug.cgi?id=1858373

Comment 2 Cédric Jeanneret 2020-08-04 14:46:18 UTC

Upstream proposal: https://review.rdoproject.org/r/#/c/28853/

We probably want the same downstream.

Comment 3 Julie Pichon 2020-08-06 07:05:49 UTC

I think we want a minor version limit as well. Updates to 16.1 are getting set up with the wrong module streams, causing a podman version that's too old to get picked up (and with which new instances can't spawn).

https://bugzilla.redhat.com/show_bug.cgi?id=1866290
https://bugzilla.redhat.com/show_bug.cgi?id=1866479

We need podman-1.6.4-15 or higher.

Comment 5 Lon Hohberger 2021-02-16 14:03:25 UTC

Without turning things into modules, there's no simple way to hard-require modular content. Cedric and I had a proposal to fail the RPM transaction without the proper module stream being present, but it was rejected.

If we wanted, we could build a modular build of something - say, python-tripleoclient - with nothing in it but python3-tripleoclient.

That module could depend on specific module streams we need. This would fail the transaction if the incorrect module streams were enabled. However, it will not obviate any steps for the customer; they will still have to manually enable the correct modular streams as defined in our documentation.

There are other possibilities in flight at the moment, such as providing metadata that can be utilized via the validations framework.

Comment 8 Miguel Garcia 2022-01-13 10:33:05 UTC


*** This bug has been marked as a duplicate of bug 1878187 ***