Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1070088

Summary: Community branding in web console
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Nikoleta Hlavickova <nziakova>
Component: Web ConsoleAssignee: Paul Gier <pgier>
Status: CLOSED CURRENTRELEASE QA Contact: Jakub Cechacek <jcechace>
Severity: urgent Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.3.0CC: brian.stansberry, dosoudil, hbraun, hpehl, jkudrnac, kkhan, nziakova
Target Milestone: DR2   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-28 15:24:27 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:
Embargoed:
Attachments:
Description Flags
Web Console in EAP 6.3.0 DR1 none

Description Nikoleta Hlavickova 2014-02-26 08:43:59 UTC 
Created attachment 867855 [details]
Web Console in EAP 6.3.0 DR1

Description of problem:
Web console contains WildFly logo instead of EAP product one.

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

How reproducible:
always

Steps to Reproduce:
1. start EAP 6.3.0 DR1
2. add a user
3. log into web console at http://localhost:9990 

Actual results:
WildFly logo on top of the page

Expected results:
EAP product logo is displayed

Additional info:
See attached screenshot.
Comment 1 Harald Pehl 2014-02-26 08:55:09 UTC 
Was caused by incorrect build parameters. Doesn't affect the functionality in any way and will change for DR2. I'm proposing to close this as DR2 is going to be released soon.
Comment 2 Harald Pehl 2014-02-27 20:46:59 UTC 
I did some research on how the last versions of the console were build and handed over to QA / productization. It turned out that we've always build the community version and deployed that version to Nexus. The reason for this is that we have to open pull requests (component upgrades) for both upstream and EAP, which refer to the same console artifact / version.

During productization the console was rebuilt using the product profile (-Peap) and deployed as special version to a custom repository. It seems that this step was skipped for DR1, which in turn led to this error. 

Could you please make sure that the console is rebuild with the EAP profile for DR2.
Comment 3 Nikoleta Hlavickova 2014-03-05 07:50:06 UTC 
I do not understand what info you need. I cannot make sure about the build but Paul who is from productization team has taken over this issue so I think he will do it.
Comment 4 Harald Pehl 2014-03-05 08:59:45 UTC 
Yes I already talked to Paul. He will take care of applying the right profile.
Comment 5 Vladimir Dosoudil 2014-03-05 13:28:03 UTC 
HAL core 2.2.0.Beta3-redhat-1
MEAD build: https://brewweb.devel.redhat.com/buildinfo?buildID=340136

HAL release-stream 2.2.0.Beta3-redhat-1
MEAD build: https://brewweb.devel.redhat.com/buildinfo?buildID=340148

PR for EAP 6.x: https://github.com/jbossas/jboss-eap/pull/1019
Comment 6 Nikoleta Hlavickova 2014-03-06 09:51:34 UTC 
Verified with EAP 6.3.0 DR2.