Bug 831168

Description of problem:


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


How reproducible:


Steps to Reproduce:
Launch from monitor page:
1.launch a mock application by selecting invalid cloud resource cluster from monitor page.
For example I was trying to launch mock application by selecting cloud resource cluster for rhevm provider. see attached screenshot.

Proper err message is displayed and the launch button is disabled.
The application does not goes in create failed state.
  

Launch from deployable page:
Now Launch the mock application by selecting invalid cloud resource cluster from deployable page.

when launched from deployable page, the launch button is not disabled and when clicked on launch the application goes in create failed state.see attched screenshots.


Actual results:
So there is an inconsistency in launch button behaviour.launch button is disabled in monitor page and enabled in deployable page.

Expected results:
if the application is eithr launched from monitor page or deployable page,the launched button should be disabled.


Additional info:
rpm  -qa | grep aeolus
aeolus-configure-2.5.7-1.el6_3.noarch
aeolus-conductor-0.8.27-1.el6_3.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.3.3-1.el6_3.noarch
aeolus-all-0.8.27-1.el6_3.noarch
aeolus-conductor-doc-0.8.27-1.el6_3.noarch
aeolus-conductor-daemons-0.8.27-1.el6_3.noarch