Bug 845363
Summary: | Bundle Deployment - Newly created Resource group which contains ~100 resources is not being <discovered> during the destination creation | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Armine Hovsepyan <ahovsepy> |
Component: | Agent | Assignee: | Jirka Kremser <jkremser> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 4.5 | CC: | hrupp, jkremser, lzoubek, mfoley |
Target Milestone: | --- | ||
Target Release: | RHQ 4.6 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-31 10:11:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Armine Hovsepyan
2012-08-02 19:44:14 UTC
There are additional requirements for a group to be listed among possible destinations. 1. group must be compatible => contains only resources having same resourceType (say platforms, or EAP6 Standalone servers) 2. given resource type must support bundle deployment (for example EAP6 Datasource has not such support, so if you create a group of datasources it won't be listed) If a user does not know these 2 things, he gets confused. I think there should be some improvement in this area. Either the wizard for a new group should be telling you these 2 conditions, or better, wizard should not allow you to create a group that does not meet these conditions. fixed in master http://git.fedorahosted.org/cgit/rhq/rhq.git/diff/?id=108eb7c9d time: Tue Jan 22 18:16:52 2013 +0100 commit: 108eb7c9d959ddf9bee65069eae79a50ac28498a author: Jirka Kremser - jkremser message: [BZ 845363 - Bundle Deployment - Newly created Resource group which contains ~100 resources is not being <discovered> during the destination creation] The Bundle Deployment Wizzard doesn't let the user to create a mixed group or a compatible group with a resource type which can't serve for deployments. The check is done using the ResourceTypeRepository. I18n and l10n added. verified on Version: 4.7.0-SNAPSHOT Build Number: bd0c492 - when a new group is created and is not compatible & does not support bundle dpeloyments - warn message is popped up. Bulk close of old bugs in VERIFIED state. |