Description of problem: A customer has reported an Octavia issue which is explained in bz 1936955 . This issue was caused by the change made in the latest podman 1.6.4-19 . It turned out that overcloud deploy(not update) triggers update of podman package and this "unexpected" update resulted in the situation. IMO 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 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Deploy overcloud 2. Run deploy again Actual results: podman package is updated Expected results: podman package is not updated after 2nd deployment Additional info:
I'm afraid usage of "latest" here is the cause. https://github.com/openstack/tripleo-ansible/blob/00f09d98dad7bf65838144f3299d1ea4449d8e8b/tripleo_ansible/roles/tripleo-podman/tasks/tripleo_podman_install.yml#L27
Redeployed OC and verified podman version did not changed
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.7 (Train) 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/RHBA-2021:3762