Bug 1083548

Summary: deploying war to domain mode (all manged servers) lead to infinite discovery scan operation run
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: ProvisioningAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED WORKSFORME QA Contact: Mike Foley <mfoley>
Severity: urgent Docs Contact:
Priority: urgent    
Version: JON 3.2CC: loleary, lzoubek, mfoley, myarboro, spinder
Target Milestone: ---   
Target Release: JON 3.2.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-03 15:45:04 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:
Bug Depends On:    
Bug Blocks: 1034218    
Attachments:
Description Flags
agent.log
none
discovery_infinite_loop
none
apache_snmp_connection-agent.log.png2 none

Description Armine Hovsepyan 2014-04-02 12:51:18 UTC
Created attachment 881772 [details]
agent.log

Description of problem:
deploying war to domain mode (all manged servers) lead to infinite discovery queue operation run

Version-Release number of selected component (if applicable):
jon 3.2.1 CP (01.04)

How reproducible:
always

Steps to Reproduce:
1. install jon 3.2.0
2. apply CP to 3.2.0
3. have EAP 6 in domain mode
4. deploy ear (see attachment in BZ #1034218) as domain deployment
5. assign it to all server groups
6. run discovery


Actual results:
discovery scan stays in InProgress state forever
exceptions in agent.log

Expected results:
discovery run finishes, eap sub-directories/sub-resources discovered

Additional info:
screen-shot attached
fragment from agent.log attached

Comment 1 Armine Hovsepyan 2014-04-02 12:52:42 UTC
Created attachment 881773 [details]
discovery_infinite_loop

Comment 2 Libor Zoubek 2014-04-02 13:07:48 UTC
According to stactrace this seems to be caused by switchyard plugin (but may required a fix in AS7 plugin as well). Could you please re-test without having switchyard plugin installed?

Comment 3 Armine Hovsepyan 2014-04-02 14:44:56 UTC
Created attachment 881830 [details]
apache_snmp_connection-agent.log.png2

Comment 4 Armine Hovsepyan 2014-04-02 14:49:30 UTC
removing switch-yard plugin fixed discovery job (it finishes)  - the warnings are still visible in agent.log

Comment 5 Simeon Pinder 2014-04-02 16:30:55 UTC
Ok. So to me that means that we need to file another bz or reassign this bz to the fsw team? @Mike Foley, what do you think here? 
That means that the version of plugin pack that was deployed with this server will throw errors on agent and cause infinite discovery(defined above) when deployed after cumulative patch 1.  This is bad and should be addressed by an updated plugin pack request I think that may need to be released at same time as the cumulative patch?  
@Armine can we get more details about the plugin pack contents that were deployed onto the server. If it's the same plugin pack that is available with the 3.2.0.GA release then the above applies.  If it's the latest plugin pack that was released with FSW, then it's a slightly smaller impact but still bad. 

CC'ing GSS as well.

Comment 6 Larry O'Leary 2014-04-02 20:00:03 UTC
This doesn't appear to be a 3.2.1 regression and most likely existed in 3.2.0.GA and is being re-targeted to 3.2.2.

This also appears to indicate that the latest FSW update-01 for 3.2 introduces a regression and may require a separate FSW BZ.

Comment 7 Mike Foley 2014-04-03 14:37:05 UTC
action item: QE/Armine retest with JON 3.2 GA.

if the issue repros on JON 3.2 GA ... 
-we need a new BZ. and then escalate that BZ with FSW
-we can close this 
-this does not block JON 3.2.1


if the issue does not repro on JON 3.2 GA
-this issue is blocking on JON 3.2.1
-assign target to JON 3.2.1
-this issue blocks JON 3.2.1

Comment 8 Armine Hovsepyan 2014-04-03 15:45:04 UTC
retested with 3.2.0 GA and 3.2.0 CP1 (#2 build) - cannot reproduce  anymore, closing as works for me.