Bug 837110

Summary:	[Agent RPM] Upgrade/Downgrade does not kill the old version of process before installation
Product:	[JBoss] JBoss Operations Network	Reporter:	Zhengping Jin <zjin>
Component:	Agent	Assignee:	Stefan Negrea <snegrea>
Status:	CLOSED NOTABUG	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	low
Version:	JON 3.1.0	CC:	snegrea
Target Milestone:	---
Target Release:	JON 3.1.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-03 22:40:39 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:	837381

Description Zhengping Jin 2012-07-02 20:01:07 UTC

Description of problem:
the agent rpm does not have a script to kill the old running process before upgrade/downgrade the agent.

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

How reproducible:
100%

Steps to Reproduce:
1. running the old version of agent, such as 3.0.0
2. upgrade the agent to version 3.1.0
3. run the new version of agent
  
Actual results:
The agent will restart after the upgrade / downgrade.
"Agent will be restarted soon to see if the failure condition cleared up
"
but after that, it still runs the old version.

Expected results:
The old version of running agent should be kill before upgrade or downgrade

Additional info:

Comment 1 Zhengping Jin 2012-07-02 20:16:05 UTC

In addtition to the actual result, both of two agents (old and new) will running.

Comment 2 Charles Crouch 2012-07-03 14:38:40 UTC

We should investigate level of effort here at least.

Comment 3 Stefan Negrea 2012-07-03 22:39:34 UTC

JON 3.1.0 agent RPM has the service shutdown command as part of the pre-uninstall script. This is a non-issue since 3.1.0 would the first release to be published and the script would be there from the first version. 

It is not advisable to have support for mixed environments (regular agent installs then RPM installs on the same system) because the extra added complexity. The general guidelines are that RPM installations and upgrade paths are the only supported within the context of RPMs. Having special code that handles cases where software is already on the system but installed outside of the RPM process is not advisable.