Description of problem: Config state files(with md5sum) of tripleo ha services created during update run have unexpected file suffixes. As a result any day-2 operation after completed update may result with pacemaker resources being restarted due to mismatch of md5sum in correct state file. Deployment playbooks check files with correct suffixes. Version-Release number of selected component (if applicable): How reproducible: Always in environment with cinder volume and cinder backup services. Steps to Reproduce: 1.Deploy OSP 2.Run OSP update 3.Run overcloud deployment to apply config change, not related to pacemaker resources Actual results: Pacemaker resources are being restarted Expected results: pacemaker resources are not being restarted, without changes to their configs Additional info: This is the same behaviour as observed in osp16.2, but we don't have converge step in 17.1. https://bugzilla.redhat.com/show_bug.cgi?id=2255233
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 (Moderate: openstack-tripleo-heat-templates and tripleo-ansible update), 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/RHSA-2024:2736