Bug 535976 (RHQ-375)

Summary: Improve handling of groups with mixed availability (like config update)
Product: [Other] RHQ Project Reporter: Jay Shaughnessy <jshaughn>
Component: InventoryAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 1.0Keywords: Improvement
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-375
Whiteboard:
Fixed In Version: 1.2 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Any
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jay Shaughnessy 2008-04-24 21:23:00 UTC
If I create a compatible group of resources I can then manipulate group members in various ways because they have the same resource type.  As an example,  performing a plugin config update for a group of JBAS servers, setting the shutdown method.

If I attempt to do this when one or more of the resources is unavailable it will almost certainly fail.  The failure generates a massive stack trace, displayed in the update detail for the failure, that I think boils down to the resource being unavailable (is this is specific to JBAS servers?).  Also, it can cause a long "in-progress" state for the update.

Perhaps the user should be warned before, or prevented from, performing certain manipulations on groups with mixed availability.

Comment 1 Joseph Marques 2009-02-04 22:28:04 UTC
we should talk about how to visually / verbally tell the user what's going on here for 1.2

Comment 2 Jay Shaughnessy 2009-02-24 02:46:15 UTC
Although there may still be some weaknesses here the overall mechanism is much improved with asynch update execution and lots of othr improvements to config update.  Let's close this and defer to other, future jiras, if any.

Comment 3 Red Hat Bugzilla 2009-11-10 21:08:00 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-375