Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1867920

Summary: overcloud export command exports the generated password values even if user provided values were set
Product: Red Hat OpenStack Reporter: Eduard Barrera <ebarrera>
Component: python-tripleoclientAssignee: James Slagle <jslagle>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: high    
Version: 16.1 (Train)CC: bdobreli, dasmith, eglynn, gcharot, hbrock, jamsmith, jhakimra, johfulto, jschluet, jslagle, kchamart, mburns, mgarciac, mkrcmari, sbauza, sbekkerm, sgordon, stephenfin, vromanso
Target Milestone: z2Keywords: Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-tripleoclient-12.3.2-1.20200914164926.72161e0.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-28 15:38:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 6 James Slagle 2020-08-12 19:10:46 UTC
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.

Comment 12 Marian Krcmarik 2020-09-30 18:43:39 UTC
$ 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

Comment 19 errata-xmlrpc 2020-10-28 15:38:46 UTC
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

Comment 20 Red Hat Bugzilla 2023-09-14 06:05:37 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days