Description of problem: We've been having issues with our deployments when we rename the datacenter from Default to RHCI, and leave Cluster as Default. The Cluster gets assigned to the Default datacenter, rather than the one we wanted, and storage doesn't get set up properly. The deployment essentially hangs while it waits on the Datacenter to come up, but it isn't configured properly, so it never does without manual intervention. When Jason was manually editing the python script that gets run to try and make it work, it looked like it was ignoring the datacenter name, and just going off of what the cluster was called. Nenad has been able to deploy after keeping the datacenter name as Default, but changing the Cluster name. Version-Release number of selected component (if applicable): Tech preview Additional info:
If you rename the datacenter you must rename the cluster as well. We simply need to enforce this. From what I could see the default cluster is tied to the default datacenter and can't be moved.
This is still a problem in compose RHCI-6.0-RHEL-7-20151104.t.0.
PR here: https://github.com/fusor/fusor/pull/673
I can submit a deployment with database and cluster name set to "Default " (trailing space). The deployment then fails when the RHEV task is at 95.8%, with "Error undefined method `[]' for nil:NilClass". If I try to enter a name like "Default 1", then I get the expected warning text "must contain only 'A-Z', 'a-z', '0-9', '_' or '-' characters" and the Next button is disabled. I can also enter database and cluster names with leading spaces, so it looks like we need to add a check for leading and trailing spaces.
I can't replicate this in the development environment, I think this commit by cchase fixed it: https://github.com/fusor/fusor/commit/903cf2d986fe8396ae4f778c0e5c03721ac347b1 When I add a space to the beginning/end of the cluster or data center name, I get the validation error "must contain only 'A-Z', 'a-z', '0-9', '_' or '-' characters".
Please re-test, we think this is now addressed.
Verified on QCI-1.2-RHEL-7-20160705.t.1.
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. https://access.redhat.com/errata/RHEA-2016:1862