Bug 771777

Summary:	Error Retrieving and Updating Backing Content for Webapp with Multiple Installed Packages
Product:	[Other] RHQ Project	Reporter:	Stefan Negrea <snegrea>
Component:	Core Server	Assignee:	Stefan Negrea <snegrea>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3	CC:	hrupp
Target Milestone:	---
Target Release:	RHQ 4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	789018 (view as bug list)		Environment:
Last Closed:	2013-09-01 09:59:24 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:	758753, 789018

Description Stefan Negrea 2012-01-04 22:41:02 UTC

Description of problem:
CLI methods retrieveBackingContent and updateBackingContent error if the webapp has multiple installed packages attached. A webapp should have only one installed package at any time, so under normal operation circumstances this scenario should not happen. However a database update error could result in having multiple installed packages attached to a webapp. If this happens, the uses will not be able to operate on the webapp from the CLI until the database is manually corrected.

How reproducible:
Every time.

Steps to Reproduce:
1. Have a JBoss AS5, JBoss AS4, or Tomcat server inventoried
2. Manually update the database to have two installed packages attached to a webapp.
3. Use the CLI to find the webapp resource.
4. Call updateBackingContent on the webapp resource.
  
Actual results:
NPE error

Expected results:
The deployment process succeeds and the database is corrected during discovery.

Additional info:
The scenario described has a high occurrence chance with the old version scheme (eg. version=1.0). The scenario is very unlikely to happen with the new version scheme (eg. version=[sha256=abcd123]) however the risk is still present.

Comment 1 Stefan Negrea 2012-02-09 15:52:46 UTC

master branch commit:

http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=c59b59bdcd6d2d33cc6cce212aee971616fb00aa

Comment 2 Heiko W. Rupp 2013-09-01 09:59:24 UTC

Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.