Description of problem: The undercloud is using the same password for [DEFAULT]/transport_url and [olso_messaging_notification]/transport_url. When you install the minion, different passwords are used for each causing amqp connection problems Version-Release number of selected component (if applicable): [cloud-user@undercloud ~]$ rpm -qa | grep tripleoclient python3-tripleoclient-12.3.2-0.20200405044622.fdce01f.el8ost.noarch python3-tripleoclient-heat-installer-12.3.2-0.20200405044622.fdce01f.el8ost.noarch How reproducible: every time Steps to Reproduce: 1. Follow https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html/director_installation_and_usage/installing-undercloud-minions 2. 3. Actual results: Passwords are not the same and there are errors in the heat-engine logs Expected results: Passwords should be consistent and no errors in the heat-engine logs Additional info:
The workaround is to update the [oslo_messaging_notification]/transport_url to be the same as the [DEFAULT]/transport_url
I'm uncertain if the bug is on the undercloud side in that the notification password should be different or if it's not properly being picked up during the minion deploy.
The workaround would be to change the NotifyPassword in the tripleo-undercloud-passwords.yaml used on the minion to match the RpcPassword prior to installation.
Overcloud successfully deploys when using minion now. Logs are: https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/DFG/view/df/view/rfe/job/DFG-df-rfe-16.1-virsh-1cont_1comp_1ceph-minion-verification/8/
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 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/RHEA-2020:4284