Bug 801812

Summary:	Upgrade from 3.0.0.GA to 3.0.1.CR6 - Failed to register server plugins NPE when changing Server Name field in installer
Product:	[Other] RHQ Project	Reporter:	Charles Crouch <ccrouch>
Component:	Core Server, Installer, Plugins	Assignee:	Deon Ballard <dlackey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	4.3	CC:	fbrychta, hbrock, hrupp, lzoubek
Target Milestone:	---
Target Release:	JON 3.0.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	801551	Environment:
Last Closed:	2012-08-10 19:14:55 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:	782579

Description Charles Crouch 2012-03-09 15:03:34 UTC

+++ This bug was initially created as a clone of Bug #801551 +++

Description of problem: I've been doing upgrade testing from JON 3.0.0.GA to JON.3.0.1.CR6. Steps to reproduce bellow are exactly what I did and may not be needed.  


Version-Release number of selected component (if applicable):
Version: 3.0.1.GA
Build Number: bf8f49a:9fe6384


Steps to Reproduce:
1.have JON 3.0.0.GA with eap & ews plugin packs
2.inventory eap 5.1.2 instance
3.upgrade to 3.0.1.GA
4.upgrade eap&ews plugins to 3.0.1.GA
  
Actual results: There is a bunch of NPEs in server log. Server plugins causing NPEs and are not upgraded to 3.0.1 -> UI stil shows 3.0.0.GA version of them


Expected results: all serer plugins are upgraded


Additional info:I am attaching 3.0.1 server log

--- Additional comment from lzoubek on 2012-03-08 15:08:12 EST ---

Created attachment 568735 [details]
3.0.1.CR6 server log

--- Additional comment from ccrouch on 2012-03-08 22:09:52 EST ---

Is this reproducible?

--- Additional comment from lzoubek on 2012-03-09 06:50:50 EST ---

It is reporducible. But, I forgot to mention one important thing. I have changed "Server name" field  on installation jsf page when upgrading to 3.0.1. Without changing "Server Name" this issue does not happen.

--- Additional comment from ccrouch on 2012-03-09 10:02:58 EST ---

Given Libor's comment: "I have changed "Server name" field  on installation jsf page when upgrading to 3.0.1. Without changing "Server Name" this issue does not happen." I don't see this as a blocker for 3.0.1. 

We should probably just reset the "Server Name" field and whatever other fields we don't support change on upgrades, when the upgrade option is selected. I'll leave this bug open for that, but drop the priority and take the target release off

In the meantime I'll raise a doc BZ for 3.0.1 to tell people not to change the "Server Name" field when upgrading.

Comment 1 Deon Ballard 2012-03-10 21:55:06 UTC

Added a warning box to the upgrade procedure and I added a Q in the "troubleshooting" Q&A in the install guide.

This is also listed now as a known issue for the 3.0.1 release notes.

Comment 2 Deon Ballard 2012-06-28 15:55:22 UTC

Oh, right, links:

* http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/3.1_Release_Notes/Known-Issues-with-this-release.html#upgrade-install-issues

* http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/Installation_Guide/troubleshooting.html#qa.301-upgrade-npe

Comment 3 Filip Brychta 2012-08-09 09:01:15 UTC

Verified links from comment 2 and known issue for the 3.0.1 release notes.