Red Hat Bugzilla – Bug 695810
Unable to schedule operation from context menu in group tree
Last modified: 2013-09-02 03:15:54 EDT
Description of problem: When I view a group tree for an EAP 5 group, and select the restart operation from the context menu for a webapp, nothing happens. But when viewing the resource tree for a platform and select the restart operation from the context menu, I am taken to the Create New Operation Schedule page. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create a compatible group of JBoss servers. 2. Select Inventory from the top-level nav. 3. Select Compatible Groups from the lower left. 4. Find and click on your JBoss AS group. 5. When the resource tree is rendered, right click on the root node, select Operations, then Restart. Actual results: Nothing happens Expected results: Should be taken to the Create New Operation Schedule page. Additional info:
Perhaps related: when the operation from the context menu is selected, it can not be scheduled the save/schedule button is disabled. Selecting a different operation in the operations dropdown enables the save/schedule button.
The first thing I notice is what Heiko reports above: for context menu launched operation scheduling (group or resource tree), the schedule button is disabled. To enable it you actually need to reselect the operation. Starting there...
While working the above "schedule button disabled" issue I see also that the reset button does not really work at all. Looking into whether that is fixable or whether we may want to remove that button.
master commit: b08cf4047af122f3e9ece38a390d4cec36905d9f OK, I think everything is resolved, the schedule button should enable and disable correctly and should play with the reset button. The reset button should properly reset to no "selection" if you came in through the New button, or to the originally selected operation if you came in through the context menu. Also, it should also remove/reset description and operation argument stuff. The operation names should not be sorted. Of course you should also be able to actually get the operation scheduled. Should test the Operation-Schedules->New button as well as the tree Context menu approach for resources, compat groups and autogroups.
Moving back to ON_DEV because there is one more bug I see that I want to tack on here. I know, I know, should be different BZs... If any of the QA fails please create a new BZ for the specific bug and set this one to verified. I;ll describe the last problem in another comment.
Back to ON_QA with one more fix. In addition to above fixes/qa validation, also: master commit cf9bcd6d8b65eabf03c19de9c231046d493c01bf Now will not schedule job with invalid operation parameters config. Clicking the Schedule button with invalid parameter or trigger configuration will provide warning message for and wait for resolution.
verified as follows: 1) scheduling operations via right-click context menu on individual resources 2) scheduling operations via right-click context menu on compatible groups
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.