Bug 752100 - Updating a WAR after it was deployed via a bundle fails.
Updating a WAR after it was deployed via a bundle fails.
Status: NEW
Product: RHQ Project
Classification: Other
Component: Content (Show other bugs)
3.0.0 Beta1
Unspecified Unspecified
medium Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-08 09:53 EST by Robert Buck
Modified: 2011-11-09 13:53 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
Bundle (1.31 KB, application/octet-stream)
2011-11-08 09:54 EST, Robert Buck
no flags Details
Updated WAR with index.html, and updated MANIFEST.MF version number. (1.16 KB, application/octet-stream)
2011-11-08 09:54 EST, Robert Buck
no flags Details

  None (edit)
Description Robert Buck 2011-11-08 09:53:10 EST
Description of problem:

I deploy a WAR via a bundle, then I update the WAR to contain an additional file, index.html, and update the WAR via Content, but the WAR does not deploy to the managed cluster. RHQ indicates 'Already Installed', which seems to be code for, 'I did not complete.' I verify with JBoss, no redeployment log entry and the index.html file is unavailable.

Version-Release number of selected component (if applicable):

RHQ in master, EAP 5.1.

How reproducible:

Every time.

Steps to Reproduce:
1. Deploy the bundle
2. Via inventory for the EAP instance, update the content (WAR) for the hello world application
  
Actual results:

New WAR was not deployed.

Expected results:

I expected the WAR to deploy.

Additional info:

None
Comment 1 Robert Buck 2011-11-08 09:54:05 EST
Created attachment 532303 [details]
Bundle
Comment 2 Robert Buck 2011-11-08 09:54:49 EST
Created attachment 532307 [details]
Updated WAR with index.html, and updated MANIFEST.MF version number.
Comment 3 Mike Foley 2011-11-09 10:56:22 EST
mixing bundle and content sub-system.
Comment 4 Charles Crouch 2011-11-09 13:53:36 EST
I think this is a medium priority since it requires usage of two subsystems 
which are normally used separately, e.g. if you deploy via a bundle, you would 
expect to update via the bundle subsystem too

Note You need to log in before you can comment on or make changes to this bug.