Bug 1677364 - Downstream OSP15 should deploy Podman by default on the Overcloud
Summary: Downstream OSP15 should deploy Podman by default on the Overcloud
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 15.0 (Stein)
Hardware: All
OS: Linux
medium
medium
Target Milestone: Upstream M3
: 15.0 (Stein)
Assignee: Emilien Macchi
QA Contact: Marius Cornea
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-14 16:03 UTC by Emilien Macchi
Modified: 2019-09-26 10:48 UTC (History)
1 user (show)

Fixed In Version: openstack-tripleo-heat-templates-10.3.1-0.20190314080339.05f1ae0.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-21 11:20:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 637001 0 'None' ABANDONED Disable Docker by default, enable Podman by default 2020-12-09 17:10:58 UTC
Red Hat Product Errata RHEA-2019:2811 0 None None None 2019-09-21 11:20:38 UTC

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
Note You need to log in before you can comment on or make changes to this bug.