Bug 1126044

Summary: Deployment content new war cannot be displayed
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: ContentAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED EOL QA Contact: Mike Foley <mfoley>
Severity: low Docs Contact:
Priority: unspecified    
Version: JON 3.3.0CC: fbrychta, jcosta, jshaughn, loleary, mfoley, tsegismo
Target Milestone: ---   
Target Release: JON 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-20 14:58:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
war-content
none
error_on_content
none
server.log
none
agent.log none

Description Armine Hovsepyan 2014-08-01 16:49:08 UTC
Created attachment 923362 [details]
war-content

Description of problem:
Deployment content new war cannot be displayed

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

How reproducible:
always

Steps to Reproduce:
1.  Start JBoss EAP 6.1 standalone server.
2.  Start JBoss ON 3.2 system.
3.  Import JBoss EAP server into inventory.
4.  Configure connection settings for newly imported resource.
5.  Deploy jboss-as-helloworld.war to JBoss EAP server.

6.  Create test repository from Administration > Content / Repositories:

    *   *Name*: `Test Repo`

7.  From Test Repo upload a new version of helloworld WAR:

    *   *Upload File*:  jboss-as-helloworld-1.0.1.war (any WAR will do)
    *   *Type*: *File [Deployment:JBossAS7]*

8.  Subscribe the imported JBoss EAP server to *Test Repo*:
    
    1.  Under *Resources Subscribed To This Repository* click *SUBSCRIBE...* button.
    2.  For search, enter `jboss-as-helloworld.war` and set type drop-down to *Service* and click search.
    3.  Check jboss-as-helloworld.war resource which was returned.
    4.  Click *SUBSCRIBE SELECTED*.
    
9.  Navigate to the content page of the jboss-as-helloworld.war resource.
10. Select the new tab.
11. Check one of the new versions of jboss-as-helloworld.war (jboss-as-helloworld-1.0.1.war).


Actual results:
old jsf logout page is visible -- see screen-shot attached

Expected results:
deployment war data displayed

Additional info:

Comment 2 Armine Hovsepyan 2014-09-19 10:34:12 UTC
issue is visible in JON 3.3 ER03
screen-shot, server and agent logs attached

Comment 3 Armine Hovsepyan 2014-09-19 10:34:44 UTC
Created attachment 939197 [details]
error_on_content

Comment 4 Armine Hovsepyan 2014-09-19 10:35:06 UTC
Created attachment 939198 [details]
server.log

Comment 5 Armine Hovsepyan 2014-09-19 10:35:30 UTC
Created attachment 939199 [details]
agent.log

Comment 6 Thomas Segismont 2014-09-19 16:12:18 UTC
I can't reproduce on a fresh master build. It looks like you used the same environment as in Bug 1126460?

https://bugzilla.redhat.com/show_bug.cgi?id=1126460#c8

Comment 7 Armine Hovsepyan 2014-09-22 07:39:02 UTC
Yes, Environment for both BZ is the same. JON 3.3 ER03

Comment 8 Juraci Paixão Kröhling 2014-10-06 11:33:38 UTC
I was also not able to reproduce the described behavior.

Comment 11 Filip Brychta 2019-05-20 14:58:22 UTC
JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.