Bug 752100

Summary: Updating a WAR after it was deployed via a bundle fails.
Product: [Other] RHQ Project Reporter: Robert Buck <rbuck>
Component: ContentAssignee: Nobody <nobody>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: medium    
Version: 3.0.0 Beta1CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Bundle
none
Updated WAR with index.html, and updated MANIFEST.MF version number. none

Description Robert Buck 2011-11-08 14:53:10 UTC 
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 14:54:05 UTC 
Created attachment 532303 [details]
Bundle
Comment 2 Robert Buck 2011-11-08 14:54:49 UTC 
Created attachment 532307 [details]
Updated WAR with index.html, and updated MANIFEST.MF version number.
Comment 3 Mike Foley 2011-11-09 15:56:22 UTC 
mixing bundle and content sub-system.
Comment 4 Charles Crouch 2011-11-09 18:53:36 UTC 
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