This service will be undergoing maintenance at 20:00 UTC, 2017-04-03. It is expected to last about 30 minutes

Bug 846982

Summary: Unable to create content-based child resource without resource configuration
Product: [Other] RHQ Project Reporter: Lukas Krejci <lkrejci>
Component: Core UIAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.5CC: hrupp, jshaughn, lkrejci
Target Milestone: ---   
Target Release: RHQ 4.6   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-13 06:38:38 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Lukas Krejci 2012-08-09 07:30:36 EDT
Description of problem:

The GUI fails to create a content-based child resource resource of a type that doesn't have any resource and/or deployment time configuration.

Currently there doesn't seem to be any such resource type in RHQ-originating plugins, but the Hadoop plugin currently being developed adds such type, not mentioning the possibility of custom 3rd party plugins that we don't know about.

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

How reproducible:

Steps to Reproduce:
1. Have the hadoop plugin from feature/hadoop-plugin branch of RHQ repo
2. Inventory the JobTracker
3. Try to "Create Child" of the type "Job Jar"
Actual results:
Exceptions in the child creation wizard

Expected results:
Child created successfully

Additional info:

This has been fixed in the feature/hadoop-plugin branch by commit:
Author: Lukas Krejci <>
Date:   Thu Aug 9 12:16:18 2012 +0200

    Fixing the child resource creation for resource types that do not have resource configuration.
Comment 1 Jay Shaughnessy 2013-09-12 10:01:11 EDT
Perhaps this fix can be cherry picked to master?  Setting to 4.10 triage and asking Lukas for info.
Comment 2 Lukas Krejci 2013-09-13 06:38:38 EDT
Master has had this since 4.6.0 but this BZ was forgotten about. Closing.

$ git tag --contains e77ecb554662b89a0710584c45765ca6c178a941