Description of problem: The following roles do not include 'OS::TripleO::Services::Podman': CellController.yaml ComputeOvsDpdkSriov.yaml ComputeOvsDpdkSriovRT.yaml Which will cause the deployment to fail due to certain parameters not being applied, for example: In a scenario where tls is not enabled and 'DockerInsecureRegistryAddress' is not being applied to those roles, will cause Podman to fail to retrieve images. Log of failed Overcloud deployment task: http://paste.openstack.org/show/750583/ Log of Overcloud environment files auto generated: http://paste.openstack.org/show/750582/ Version-Release number of selected component (if applicable): rpm -qa | grep tripleo ansible-role-tripleo-modify-image-1.0.1-0.20190422122515.f1dfdc6.el8ost.noarch openstack-tripleo-heat-templates-10.5.1-0.20190426040357.0b61dd0.el8ost.noarch puppet-tripleo-10.4.2-0.20190426000346.bc825d0.el8ost.noarch openstack-tripleo-common-containers-10.7.1-0.20190426083235.1988c18.el8ost.noarch python3-tripleoclient-heat-installer-11.4.1-0.20190424070351.41fa2fc.el8ost.noarch openstack-tripleo-validations-10.4.1-0.20190426070346.e774685.el8ost.noarch python3-tripleo-common-10.7.1-0.20190426083235.1988c18.el8ost.noarch python3-tripleoclient-11.4.1-0.20190424070351.41fa2fc.el8ost.noarch openstack-tripleo-image-elements-10.4.1-0.20190426080346.7efbd4c.el8ost.noarch openstack-tripleo-common-10.7.1-0.20190426083235.1988c18.el8ost.noarch ansible-tripleo-ipsec-9.1.1-0.20190422122014.8c1fdab.el8ost.noarch openstack-tripleo-puppet-elements-10.3.1-0.20190426070355.a359301.el8ost.noarch How reproducible: always Steps to Reproduce: 1. Attempt to deploy Overcloud with generated roles_data for ComputeOvsDpdkSriov role (or others) Actual results: Deployment fails Expected results: Deployment passes Additional info:
Not a blocker because it can be worked around by adding OS::TripleO::Services::Podman to the affected roles.
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