Bug 1050005 - Cannot delete DomainDeployment archive
Summary: Cannot delete DomainDeployment archive
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Content
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DR03
: JON 3.2.2
Assignee: Jirka Kremser
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-08 15:35 UTC by Bill DeCoste
Modified: 2014-07-29 00:17 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-07-29 00:17:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screen shot error (48.05 KB, image/png)
2014-01-08 15:35 UTC, Bill DeCoste
no flags Details

Description Bill DeCoste 2014-01-08 15:35:36 UTC
Created attachment 847212 [details]
screen shot error

Description of problem:
When you try to delete a DomainDeployment archive per the doc, you get the attached error. /portal/portal/rhq/resource/content/confirm-delete-plain.xhtml is missing


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


How reproducible:
100%


Steps to Reproduce:
1. Spin up EAP in Domain Mode
2. Add a .war file as a DomainDeplyment to the Domain Contoller via Inventory Create Child
3. Add the .war to the main-server-group so it deploys (I don't think this is necessary)
4. Go to the .war resource, Content tab, select the .war and hit delete. 

Actual results:
Resulting screen shot error caused by missing /portal/portal/rhq/resource/content/confirm-delete-plain.xhtml

Expected results:
.war is deleted and undeployed from main-server-group


Additional info:
I tried copying ... 'cp ./modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-portal.war/rhq/resource/content/confirm-delete-plain.xhtml ./modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-portal.war/portal/portal/rhq/resource/content/' but this ended up just showing some bogus html and the .war was uneffected

Comment 1 Bill DeCoste 2014-01-08 15:41:55 UTC
Just tested with a standalone deployment and that fails the same way.

Comment 2 Jirka Kremser 2014-02-18 10:27:57 UTC
branch:  master
link:    http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?id=223562d0b
time:    2014-02-18 11:25:41 +0100
commit:  223562d0b27fda9c0f5b22f451e4c405d0b5fc0f
author:  Jirka Kremser - jkremser
message: [BZ 1050005] - Cannot delete DomainDeployment archive - Removing the
         "/portal/portal/" path prefix to make the navigation case
         working.


Needs to be cherry-picked..

Comment 3 Jirka Kremser 2014-06-09 12:20:54 UTC
cherry-picked to release branch: 6c51cddf4

Comment 4 Simeon Pinder 2014-06-30 06:03:09 UTC
Moving to ON_QA as available for test in latest build:
http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.2.GA/6-28-2014/

Comment 5 Filip Brychta 2014-06-30 09:43:02 UTC
Error reported in this bz is fixed, but a result of steps reported in description is still fail with error msg "Removal of packages backing the deployments is not supported." which should be expected.
Marking as verified
Version:
Version :	
3.2.0.GA Update 02
Build Number :	
558495c:44428f7

Comment 6 Jirka Kremser 2014-06-30 10:53:07 UTC
looking briefly to the code where the message is coming from and I found this:

        response.setOverallRequestErrorMessage("Removal of packages backing the deployments is not supported.");
...
...


        try {
            response = contentManager.performPackageDelete(request.getResourceId(), request.getPackages());
        } catch (Throwable throwable) {
            response = new RemovePackagesResponse(ContentResponseResult.FAILURE);
            response.setOverallRequestErrorMessage(ThrowableUtil.getStackAsString(throwable));
        }

So the exception is swallowed and this generic error message is printed. Not sure if it is regression or expected behavior (removing a content from content-backed resource should end up with removing also the resource, I guess), but it is a different issue than the original bug.

Comment 7 Larry O'Leary 2014-07-29 00:17:29 UTC
This has been verified and released in Red Hat JBoss Operations Network 3.2 Update 02 (3.2.2) available from the Red Hat Customer Portal[1].



[1]: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=31783


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