The issue with the wrong password being in central-export.yaml is a problem with openstack overcloud export. It assumes the "passwords" key in plan-environment.yaml are the passwords used during the deployment. One would think that would be the case, however those passwords are actually always the generated passwords regardless of if a user defined password was used or not. The export command needs to look at parameter_defaults from plan-environment.yaml to get the user defined values, and fall back to passwords if none was specified.
$ grep debug overcloud_deploy.sh -e /home/stack/central/debug.yaml \ $ grep AdminPassword /home/stack/central/debug.yaml AdminPassword: nazdar $ openstack overcloud export --force-overwrite --stack central --output-file /home/stack/new-central-export.yaml > /dev/null sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=4, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.24.2', 35040), raddr=('192.168.24.2', 13000)> sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.24.2', 34430), raddr=('192.168.24.2', 13004)> $ grep AdminPassword /home/stack/new-central-export.yaml AdminPassword: nazdar
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days