Bug 1445798 - Unable to perform any operation on an application archive in a EAP
Summary: Unable to perform any operation on an application archive in a EAP
Keywords:
Status: CLOSED DUPLICATE of bug 1443881
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Jirka Kremser
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-26 14:18 UTC by Prachi
Modified: 2017-12-12 15:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-08 12:26:28 UTC
Category: ---
Cloudforms Team: Middleware
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
selected war file options available (152.72 KB, image/png)
2017-04-26 14:18 UTC, Prachi
no flags Details

Description Prachi 2017-04-26 14:18:39 UTC
Created attachment 1274242 [details]
selected war file options available

Description of problem: Unable to perform any operation on an application archive in a EAP such as disable/enable/reload


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

5.8.0.12-rc1.20170425180304_4f35996 


How reproducible:


Steps to Reproduce:
1. login to CFME
2. Navigate to middleware >> deployments
3. select a war file 

Actual results:

Operation on application archive is not available.

Expected results:

Should be able to perform operations on EAP application archive.


Additional info:

Comment 2 Alissa 2017-04-30 13:50:01 UTC
Prachi, what is the setup in this tested environment - is eap running in a container or not?

Comment 4 Matt Mahoney 2017-05-08 12:26:28 UTC

*** This bug has been marked as a duplicate of bug 1443881 ***

Comment 6 Prachi 2017-05-12 13:41:41 UTC
>> Prachi, what is the setup in this tested environment - is eap running in a container or not?


EAP was not installed in a container. Recently verified in latest version 5.8.0.14-rc3.20170509175238_5dbf87a  and it is working fine.


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