Bug 1304324
| Summary: | openstack overcloud deploy should never generate new passwords for a stack update. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jaromir Coufal <jcoufal> |
| Component: | python-rdomanager-oscplugin | Assignee: | RHOS Maint <rhos-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | yeylon <yeylon> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | unspecified | CC: | athomas, dmacpher, dmatthew, hbrock, jslagle, mburns, nbarcet, rhel-osp-director-maint, rybrown, srevivo, vcojot, yeylon |
| Target Milestone: | y3 | ||
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
Cause: When running the command `openstack overcloud deploy` to update a deployment from a directory that wasn't used when creating the deployment the password file wont be found. This results in a new password file being generated and new random passwords will be passed to Heat.
Consequence: Heat will attempt to reconfigure the passwords for all the overcloud services, but this isn't fully supported.
Workaround (if any): Make sure that all calls to update a deployment are done from the same directory. To check you are in the correct directory, look for a file called tripleo-overcloud-passwords.
|
Story Points: | --- |
| Clone Of: | 1303681 | Environment: | |
| Last Closed: | 2016-02-09 14:51:02 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: | |||
| Bug Depends On: | 1303681 | ||
| Bug Blocks: | |||
|
Comment 1
Jaromir Coufal
2016-02-03 10:21:25 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |