Red Hat Bugzilla – Bug 1267348
Space in deployment name breaks cloudforms install
Last modified: 2016-10-03 15:29:11 EDT
Description of problem:
I named a deployment "Basic Deployment". The CloudForms install step then failed, because it couldn't bring in a template named "Basic" from the export domain.
Spelunking the logs reveals that the template in question was expected to be named "Basic Deployment-cfme-template", indicating that the space between Basic and Deployment is causing problems.
Version-Release number of selected component (if applicable):
20150829.0 < Somewhat old
I've made it happen twice in two tries, so 100% so far.
Steps to Reproduce:
1. Deploy the iso, run fusor installer, etc, to get to creating a new deployment
2. Create a new deployment with a space in its name, choosing to deploy cloudforms into rhevm
3. Wait for the deplyoment to fail when setting up CloudForms
Install fails due to template "Basic" not existing in rhevm.
Install succeeds because the expected template exists.
This a rather dated version of the installer, and I haven't tested on a newer version, but I didn't see this reported elsewhere and expect it might be an issue.
I was able to force the installation to continue by adding a template to the export domain named "Basic" and resuming the failed task.
I believe David Davis has a change in so we can labelize the deployment name and use that instead of the deployment names so problems like this don't keep cropping up.
If we want to add a (separate) label field to deployments, we can reuse katello's labelize stuff:
I don't have any sort of change in though to do this.
We put in a temporary fix to disallow deployment names with a space. RHEV doesn't allow templates to have spaces in their names.
Deployment name now cannot contain a space character. Marking as verified.