Bug 616855

Summary: Upgrade JON2.3.1 to JON2.4GA_QA with postgres is missing embedded JBossAS data (like alert)
Product: [Other] RHQ Project Reporter: Rajan Timaniya <rtimaniy>
Component: DatabaseAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact: Corey Welton <cwelton>
Severity: medium Docs Contact:
Priority: low    
Version: 3.0.0CC: hrupp, mazz, sdharane
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-21 15:53:25 UTC Type: ---
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: 601949, 614432    
Attachments:
Description Flags
server log none

Description Rajan Timaniya 2010-07-21 14:39:04 UTC
Created attachment 433439 [details]
server log

Description of problem:
Upgrade JON2.3.1 to JON2.4GA_QA with postgres is missing embedded JBossAS data (like alert).

Version-Release number of selected component (if applicable):
JON2.4 (build #71) version: 2.4.0.GA_QA build number: 10860:2ca5643

How reproducible:

Steps to Reproduce:
1) Install JON 2.3.1 and agent with Postgres 8.4
2) Perform operations on JON 2.3.1
 (i) Create alerts (for embedded JBossAS JVM):
     a)Name: JVM Alert  Type: JBoss AS JVM (Server)
	If Condition:  	 Availability goes DOWN
	Dampening Rule: 	Each time condition set is true
	Action Filters: 	Disable alert until re-enabled manually or by   
        recovery alert : false 
3) Stop/Down all JON2.3.1 servers
4) Keep agent running
7) Upgrade one server from JON2.3.1 to JON 2.4 (build #71) (with same
database-Postgres 8.4)
8) Verify all embedded JBossAS data
  
Actual results:
Upgrade JON2.3.1 to JON2.4GA_QA with postgres is missing embedded JBossAS data (like alert).

Expected results:
Upgrade JON2.3.1 to JON2.4 should migrate embedded JBossAS data.

Additional info:
Please refer attached server log.

JON2.3.1- Resource Key: /jon/jon2.3.1/jon-server-2.3.1.GA/jbossas/server/default

JON2.4- Resource Key: /jon/jontag71/jon-server-2.4.0.GA_QA/jbossas/server/default

Comment 1 Heiko W. Rupp 2010-07-21 15:53:25 UTC
pilhuhn: as we are "killing" the old and starting new resources for the new server, this VM is a new resource
[17:26] pilhuhn: and the installer can not know in advance which resource id it will get to migrate alerts over
and we have always said that customers will loose data on the old rhq server like collected metrics etc.

So closing...

Comment 2 John Mazzitelli 2010-07-21 17:39:31 UTC
this is documented here:

http://rhq-project.org/display/JOPR2/Upgrading+the+Server

in the big yellow box that says, in part:

"if you have a resource in inventory corresponding to the RHQ Server itself, upgrading RHQ will entail the loss of all data for that RHQ Server resource."