Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 866967

Summary: Cloud field gets disabled while creating a New Cloud Resource Zone if the name is duplicated
Product: [Retired] CloudForms Cloud Engine Reporter: Ramesh A <rananda>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 1.1.0CC: morazi
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
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: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Cloud-field-disabled none

Description Ramesh A 2012-10-16 12:28:31 UTC 
Description of problem:


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


How reproducible:
100%

Steps to Reproduce:
1. As Admin try to create a New Cloud Resource Zone with already existing name and click on save button
2. Observe the cloud field after the Error message is displayed
  
Actual results:
Cloud field gets disabled

Expected results:
Cloud field should not be disabled.

Additional info:
rpm -qa|grep aeolus
aeolus-conductor-0.13.18-1.el6cf.noarch
aeolus-conductor-daemons-0.13.18-1.el6cf.noarch
aeolus-configure-2.8.9-1.el6cf.noarch
aeolus-all-0.13.18-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-doc-0.13.18-1.el6cf.noarch
rubygem-aeolus-cli-0.7.4-1.el6cf.noarch
Comment 1 Ramesh A 2012-10-16 12:30:34 UTC 
Created attachment 628144 [details]
Cloud-field-disabled