Created attachment 570254 [details] rails log Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Login ton conductor 2.go the monitor 3.try to create one more "Default" cloud resource zone 4.It will display message "Cloud Resource Zone creation failed. Errors Header Name has already been taken" 5.Now try changing the name of cloud resource zone to "test" from the same page Actual results: It displays "Cloud Resource Zone creation failed. Errors undefined method `name' for nil:NilClass" Expected results: User should be allowed to change duplicate name to a new one during cloud resource zone creation. Additional info: Attached rails log. rpm -qa | grep aeolus aeolus-configure-2.5.0-18.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.3.0-14.el6.noarch aeolus-conductor-0.8.0-43.el6.noarch aeolus-conductor-doc-0.8.0-43.el6.noarch aeolus-conductor-daemons-0.8.0-43.el6.noarch aeolus-all-0.8.0-43.el6.noarch
I reproduced this as well
I think what's happening is that we're dropping the pool_family_id when we re-render the form after the error, so @pool.pool_family is nil. I'm going to see if we can carry this value through.
Patch on list: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-March/009627.html
Pushed to master: commit 8ac4f20c752d9b590a39f0e32e4aa8f380b48b3d Author: Matt Wagner <matt.wagner> Date: Mon Mar 19 13:49:01 2012 -0400 BZ 803647 - Persist pool[pool_family_id] on failure during creation If you hit a validation error while creating a pool, we need to keep your pool_family_id attribute or else you will receive an exception when you try to save a second time, because pool_family_id is nil.
8ac4f20c752d9b590a39f0e32e4aa8f380b48b3d is only on master as of this writing.
Moving this to 1.0.z/1.1, it is not a blocker.
Observed that now this error is not displayed, and user was able to create a new CRZ. verified on: rpm -qa | grep aeolus aeolus-configure-2.5.3-1.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-conductor-doc-0.8.12-1.el6_2.noarch aeolus-conductor-daemons-0.8.12-1.el6_2.noarch aeolus-all-0.8.12-1.el6_2.noarch aeolus-conductor-0.8.12-1.el6_2.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch
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. http://rhn.redhat.com/errata/RHEA-2012-0583.html