Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1078479

Summary: agent cannot discover platform (send avail repo to) for first couple minutes
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: UpgradeAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: jshaughn, loleary, mfoley, spinder
Target Milestone: ---   
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-29 19:37:38 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:
Attachments:
Description Flags
agent.log none

Description Armine Hovsepyan 2014-03-19 18:33:01 UTC
Created attachment 876558 [details]
agent.log

Description of problem:
[CP1] agent cannot discover platform (send avail repo to) for first couple minutes 

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

How reproducible:


Steps to Reproduce:
1. install jon 3.2 
2. apply patch


Actual results:
Failure during discovery for [Query Cache] Resources - failed after 65 ms.

Expected results:
no exception in agent.log

Additional info:
agent.log attached

Comment 3 Simeon Pinder 2014-03-25 19:24:16 UTC
Moving this back to general triage as looks to be startup delay only as worked fine after.

Comment 4 Larry O'Leary 2014-03-25 19:26:20 UTC
Based on a call I had with QE early today, the concenses was that the server was still starting up and that the agent was not able to send it availability report yet. After the server went online, the agent started working correctly.

If anything, we should probably make this more clear in the agent log so a user understands that the agent is unable to communicate with the server due to the server being offline.

Comment 6 Jay Shaughnessy 2014-08-29 19:37:38 UTC
I'm not aware any actual problem here.