Bug 805224 - Repeatedly clicking "restart" for an application triggers errors in vsphere
Summary: Repeatedly clicking "restart" for an application triggers errors in vsphere
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
Assignee: Tomas Hrcka
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-20 16:56 UTC by Corey Welton
Modified: 2012-12-04 15:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Repeatedly clicking "Restart" for an application triggered errors in the vSphere console. This update sets the correct error message to be displayed in Conductor and not the vSphere console when users click the "Restart" button more than one time.
Clone Of:
Environment:
Last Closed: 2012-12-04 15:00:17 UTC


Attachments (Terms of Use)
Reboot clicked twice -> error (73.02 KB, image/png)
2012-09-25 16:28 UTC, Ronelle Landy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:1516 0 normal SHIPPED_LIVE CloudForms Cloud Engine 1.1 update 2012-12-04 19:51:45 UTC

Description Corey Welton 2012-03-20 16:56:24 UTC
Description of problem:

When a user "accidentally" double-clicks (or more) Restart in order to reboot an application in vsphere, errors get thrown on the vsphere console.  

Most likely, the Restart button should be disabled onclick so that multiple commands cannot be sent.

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


How reproducible:


Steps to Reproduce:
1.  Administer > Content > $catalog > Application Blueprints.
2.  Select a blueprint that is "green" for vsphere (?); Launch
3.  On the ensuing screen, Launch
4.  Monitor > Your Cloud Zone > $application
5.  After application appears to be up and running (has IP, etc.), "accidentally" double- or triple-click the Restart button  

Actual results:
error thrown in vsphere console.

Expected results:
No errors - can probably be avoided simply by disabling the reset button onclick

Additional info:

Comment 1 Hugh Brock 2012-03-23 14:52:12 UTC
Too complex for 1.0. MOving to z.

Comment 5 Ronelle Landy 2012-09-25 16:28:22 UTC
Tested rpms:

>> rpm -qa |grep aeolus
aeolus-configure-2.8.7-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.7.2-1.el6cf.noarch
aeolus-conductor-0.13.14-1.el6cf.noarch
aeolus-conductor-daemons-0.13.14-1.el6cf.noarch
aeolus-conductor-doc-0.13.14-1.el6cf.noarch
aeolus-all-0.13.14-1.el6cf.noarch

Double clicking the 'Restart' button results in the folllowing correct error in Conductor

**************

 Errors
The Instance ce-2h6kn/testVsphere was not rebooted because reboot is already scheduled. 

**************

See attached screenshot - no errors were visible in the vsphere console.

Marking this BZ as 'verified'.

Comment 6 Ronelle Landy 2012-09-25 16:28:59 UTC
Created attachment 617131 [details]
Reboot clicked twice -> error

Comment 8 errata-xmlrpc 2012-12-04 15:00:17 UTC
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-1516.html


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