Bug 854533 - "That name already in use" is displayed for blank deployment name.
"That name already in use" is displayed for blank deployment name.
Status: NEW
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: aeolus-conductor (Show other bugs)
1.1.0
Unspecified Unspecified
medium Severity low
: rc
: ---
Assigned To: Angus Thomas
Rehana
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-05 05:40 EDT by Aziza Karol
Modified: 2012-09-07 10:39 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
err (41.78 KB, image/png)
2012-09-05 05:40 EDT, Aziza Karol
no flags Details

  None (edit)
Description Aziza Karol 2012-09-05 05:40:14 EDT
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.install aeolus.
2.login to conductor and in default pool, click on new deployment.
3.keep the deployment name as blank and click on next button.
  
Actual results:
"That name is already in use" is diplayed even if the deployment name is blank.see attached screenshot.

Expected results:
proper validation required to handle blank deployment name.

Additional info:
rpm -qa | grep aeolus
rubygem-aeolus-image-0.6.0-0.20120905040030git902c81c.fc16.noarch
rubygem-aeolus-cli-0.7.0-0.20120905040026gitd64d64f.fc16.noarch
aeolus-conductor-daemons-0.13.0-0.20120905080008gite6cb571.fc16.noarch
aeolus-conductor-doc-0.13.0-0.20120905080008gite6cb571.fc16.noarch
aeolus-configure-2.8.0-0.20120905040024git040c5ef.fc16.noarch
aeolus-conductor-0.13.0-0.20120905080008gite6cb571.fc16.noarch
aeolus-all-0.13.0-0.20120905080008gite6cb571.fc16.noarch
Comment 1 Aziza Karol 2012-09-05 05:40:58 EDT
Created attachment 609952 [details]
err

Note You need to log in before you can comment on or make changes to this bug.