Red Hat Bugzilla – Bug 789018
Error Retrieving and Updating Backing Content for Webapp with Multiple Installed Packages
Last modified: 2013-09-03 11:15:29 EDT
+++ This bug was initially created as a clone of Bug #771777 +++
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.
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.
The deployment process succeeds and the database is corrected during discovery.
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.
release/jon3.0.x branch commit:
Moving to ON_QA as new RC 4 available to test in:
According to Stefan's advice on IRC I've Performed these steps:
1.have deploymnet hello.war( id=1000 ) on EAP4
- select * from rhq_installed_package where resource_id=1000 returns 1 row
2. created another row in rhq_installed_package having same resource id, but different package_version_id
- UI then shows 2 different installed packages for hello.war resource
3. deployed hello.war using content subsytem
- UI do longer displays 2 installed packages
- select * from rhq_installed_package where resource_id=1000 returns 1 row and refers to new package_version_id, the old rows in rhq_package_version still exist
Bulk closing of old issues in VERIFIED state.