podman package is updated during deployment

[Takashi Kajinami]

Description
===========

This issue was initially reported in https://bugzilla.redhat.com/show_bug.cgi?id=1942273

It turned out that overcloud deploy(not update) triggers update of podman package.

We should not trigger any package update during deployment.
Especially for podman we have experienced some issues caused by its change thus should ensure that the package is not updated unless the proper minor update is executed

Some prose which explains more in detail what this bug report is
about. If the headline of this report is descriptive enough, skip
this section.

Steps to reproduce
==================
1. Deploy overcloud
2. Downgrade podman package
3. Run deployment again to update the existing overcloud

Expected result
===============
Podman package is not updated after the second deployment

Actual result
=============
Podman package is updated after the second deployment

Environment
===========
This issue was initially found in a downstream distribution based on stable/train.
But there exists a logic to pull the latest podman package thus we are likely to have the same issue in master.

https://github.com/openstack/tripleo-ansible/blob/00f09d98dad7bf65838144f3299d1ea4449d8e8b/tripleo_ansible/roles/tripleo-podman/tasks/tripleo_podman_install.yml#L27

Logs & Configs
==============
N/A

[Takashi Kajinami (kajinamit)]

I have proposed a fix to master. https://review.opendev.org/c/openstack/tripleo-ansible/+/782631

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 1.5.3 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 3.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 2.3.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 0.8.0 release.