Bug 1858372

Summary: [osp16.1]remove podman-docker package from the OC image
Product: Red Hat OpenStack Reporter: Paras Babbar <pbabbar>
Component: openstack-tripleo-puppet-elementsAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: low    
Version: 16.1 (Train)CC: apevec, bdobreli, emacchi, hbrock, jslagle, mburns
Target Milestone: z3Keywords: Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-puppet-elements-11.2.2-1.20200916223429.f061f90.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-15 18:35:45 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 Paras Babbar 2020-07-17 17:15:47 UTC
Description of problem:
We have seen podman-docker package being included in 16.1 OC image and while on 13-16.1 upgrade podman-docker was not found for bith uc/oc image.


On 16.1 deployment:
UC Node: podman-docker package not found
OC Node: podman-docker package was available

On 13-16.1 Upgrade:
UC/OC Node: podman-docker package not found

However on the functionality , we haven't see any impact. So not sure if we would like to remove it from the tripleo deployment OC image as well.

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

How reproducible:
everytime

Steps to Reproduce:
1.go to oc/uc image
2.found podman-docker on OC image while on upgrade to 16.1 it's not visible


Actual results:


Expected results:


Additional info:

Comment 12 errata-xmlrpc 2020-12-15 18:35:45 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 (Red Hat OpenStack Platform 16.1.3 bug fix and enhancement 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-2020:5413