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
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...
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."