Description of problem:
Issues such as bug 1395810 means the user has to go update parameters for the different roles. This causes an extra parameter (CloudDomain) to be silently modified and saved to an empty string, causing FQDN to become unresolvable and leading every deployment to fail on galera/mariadb related errors.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Click on the pencil for editing a role, e.g. Compute
2. Change any parameter (e.g. OvercloudComputeFlavor: compute), save the changes
3. The mistral environment shows another parameter was updated in addition to OvercloudComputeFlavor:
3. Only the parameters changed by the user are updated
This is happening because the default in the tripleo-heat-templates are not set per role, but only once in overcloud.j2.yaml where the UI cannot get at (see comments on upstream bugs for further information).
Make sure to manually set CloudDomain to the default indicated in the doc string - localdomain - before hitting Save.
Fix landed on master, backport proposed.
The fix is located in tripleo-heat-templates so, moving the bug. (The verification will likely still need to be done using the UI though.)
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.