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

Bug 1249136

Summary:	Agent auto upgrade fails because a jar install is installed to the default rpm directory
Product:	[JBoss] JBoss Operations Network	Reporter:	dsteigne
Component:	Agent	Assignee:	Simeon Pinder <spinder>
Status:	CLOSED NOTABUG	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	JON 3.3.3	CC:	dsteigne, fbrychta, loleary
Target Milestone:	---
Target Release:	JON 3.3.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 15:12:43 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 dsteigne 2015-07-31 15:21:36 UTC

Description of problem:
Is there another way to check for an agent rpm install? If the customer just happens to install a jar agent installation to the default rpm directory /opt/jon/rhq-agent the upgrade fails with "An agent RPM installation was found in .."

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Larry O'Leary 2015-11-19 15:12:43 UTC

After reviewing the information from the original report, it has been determined that there may have been a misunderstanding regarding the message.

The message does not indicate that the agent update could not be performed. It only warned that the system also included an RPM installed agent and that the apply-update utility WOULD NOT update the RPM but only the ZIP installed agent.

Closing as not a bug.