Bug 1249136 - Agent auto upgrade fails because a jar install is installed to the default rpm directory
Summary: Agent auto upgrade fails because a jar install is installed to the default rp...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Agent
Version: JON 3.3.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: JON 3.3.5
Assignee: Simeon Pinder
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-31 15:21 UTC by dsteigne
Modified: 2019-07-11 09:44 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-19 15:12:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.