Verified , [stack@undercloud-0 ~]$ cat core_puddle_version 2019-10-21.1[stack@undercloud-0 ~]$ (undercloud) [stack@undercloud-0 ~]$ openstack stack list +--------------------------------------+------------+----------------------------------+-----------------+----------------------+----------------------+ | ID | Stack Name | Project | Stack Status | Creation Time | Updated Time | +--------------------------------------+------------+----------------------------------+-----------------+----------------------+----------------------+ | 66d82183-478d-483f-a26b-934db34e417d | overcloud | 9371bb9726184ed3986ce591fe760795 | UPDATE_COMPLETE | 2019-10-23T13:21:07Z | 2019-10-24T09:13:57Z | +--------------------------------------+------------+----------------------------------+-----------------+----------------------+----------------------+ PLAY RECAP ********************************************************************* controller-0 : ok=251 changed=99 unreachable=0 failed=0 controller-1 : ok=236 changed=90 unreachable=0 failed=0 controller-2 : ok=236 changed=90 unreachable=0 failed=0 Thursday 24 October 2019 06:54:41 -0400 (0:00:00.892) 1:24:28.326 ****** =============================================================================== Updated nodes - Controller Success (undercloud) [stack@undercloud-0 ~]$ ansible controller -mshell -b -a'docker logs haproxy_restart_bundle|grep locally' [WARNING]: Found both group and host with same name: undercloud controller-1 | SUCCESS | rc=0 >> Thu Oct 24 10:15:58 UTC 2019: Restarting haproxy-bundle locally on 'controller-1' controller-0 | SUCCESS | rc=0 >> Thu Oct 24 10:42:46 UTC 2019: Restarting haproxy-bundle locally on 'controller-0' controller-2 | SUCCESS | rc=0 >> Thu Oct 24 09:50:39 UTC 2019: Restarting haproxy-bundle locally on 'controller-2'
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/RHBA-2019:3745