Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1677364

Summary:	Downstream OSP15 should deploy Podman by default on the Overcloud
Product:	Red Hat OpenStack	Reporter:	Emilien Macchi <emacchi>
Component:	openstack-tripleo-heat-templates	Assignee:	Emilien Macchi <emacchi>
Status:	CLOSED ERRATA	QA Contact:	Marius Cornea <mcornea>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	15.0 (Stein)	CC:	mburns
Target Milestone:	Upstream M3	Keywords:	Triaged
Target Release:	15.0 (Stein)
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-10.3.1-0.20190314080339.05f1ae0.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:20:21 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 Emilien Macchi 2019-02-14 16:03:21 UTC

Description of problem:

To deploy Podman & Pacemaker together, a specific version of pcs is needed and this version isn't available in CentOS7, which is the platform used by TripleO upstream CI.

Therefore, we can't switch the default ContainerCli to podman in upstream THT.


Version-Release number of selected component (if applicable):

Upstream Stein (current master).

How reproducible:

Deploy an Overcloud, Docker will be used by default.

The plan is:

- Patch downstream THT to switch default overcloud to use Podman, as the OS is RHEL8 and has the new pcs.
- Keep upstream THT to use Docker by default on the overcloud.
- Once CentOS8 is out, we'll switch upstream to use Podman by default on the overcloud.

Comment 6 errata-xmlrpc 2019-09-21 11:20:21 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/RHEA-2019:2811