Bug 1018259

Summary: Creating Managed Server JVM hangs In Progress for ages
Product: [JBoss] JBoss Operations Network Reporter: Libor Zoubek <lzoubek>
Component: Plugin -- JBoss EAP 6Assignee: Thomas Segismont <tsegismo>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: rhatlapa, theute, tsegismo
Target Milestone: ER07   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Bug Depends On:    
Bug Blocks: 1012435    

Description Libor Zoubek 2013-10-11 14:50:57 UTC
Description of problem:

I cannot add JVM Definition child resource to new managed server. ResourceChildHistory shows  'In progress' .. and finishes after 11 minutes. After that jvm child resource is not discovered

Version-Release number of selected component (if applicable):
JON 3.2.ER3 + EAP 6{0,1,2}

How reproducible: always


Steps to Reproduce:
1. have Domain controller
2. create new managed server, do not start it
3. create JVM Definition child resource for your managed server

Actual results: ResourceChildHistory shows  'In progress' .. and finishes after 11 minutes, after that JVM is not discovered

In agent log .. I meet this 
WARN  [ResourceFactory.executor-1] (rhq.core.pc.inventory.CreateResourceRunner)- Failed to discover Resource for newly created [ResourceType[id=0, name=JVM Definition, plugin=JBossAS7, category=Service]] managed resource with key [host=master,server-config=666,jvm=jvmmm].


Expected results: JVM Definition is created and discovered instantly


Additional info: This must be some regression, I can confirm this issue could not be reproduced on JON 3.2.Alpha58. Unfortunately, I don't have results from previous ER builds, because of UI changes, some tests including this did not run at all.

Comment 1 Thomas Segismont 2013-10-17 12:58:18 UTC
Could not reproduce on a fresh master build.

Can you detail the reproduction steps? Did you create another JVM Definition (other than the "default" one) before overriding it in the Managed Server?

Now trying on a release/jon3.2.x build...

Comment 2 Libor Zoubek 2013-10-23 09:51:10 UTC
I have no other steps. I have only default JVM definition.

There is one thing, although. I run it on JON 3.2 with all plugins, and I see lots of error messages caused by switchyard plugin Bug 1018270.

As those errors happen in discovery, it might be reason for this bug.

I tried to reproduce it again .. and even adding managed server took 3minutes, and adding JVM under it took 11 minutes

Is it possible that create-child-operation might be blocked by service discovery scan?

Comment 3 Thomas Segismont 2013-11-07 10:22:06 UTC
Fixed in master

commit 71556e140266f819f97342b24f40aaa9ace6ffd0
Author: Thomas Segismont <tsegismo>
Date:   Thu Nov 7 11:19:09 2013 +0100

Managed server discovery/create did not return consistent resource key formats. So the resource creation process of the Managed Server was stuck and prevented the JVM Definition creation process from starting.

Comment 4 Thomas Segismont 2013-11-07 10:24:24 UTC
Cherry-picked to release/jon3.2.x

commit f1a7c8630e7cc64ae1219efb63bb1009d27529df
Author: Thomas Segismont <tsegismo>
Date:   Thu Nov 7 11:19:09 2013 +0100

Comment 5 Simeon Pinder 2013-11-19 15:48:56 UTC
Moving to ON_QA as available for testing with new brew build.

Comment 6 Simeon Pinder 2013-11-22 05:14:22 UTC
Mass moving all of these from ER6 to target milestone ER07 since the ER6 build was bad and QE was halted for the same reason.

Comment 7 Libor Zoubek 2013-11-25 08:46:02 UTC
verified on ER7