Bug 1392330

Summary: openshift-jvm Camel Route Diagram: Totoal typo
Product: OpenShift Container Platform Reporter: Libor Fuka <lfuka>
Component: Management ConsoleAssignee: Alexandre Kieling <abrianik>
Status: CLOSED ERRATA QA Contact: Peng Li <penli>
Severity: low Docs Contact:
Priority: medium    
Version: 3.3.1CC: abrianik, aos-bugs, jokerman, maschmid, mmccomas, penli, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Typo in Camel route diagram Consequence: On hover, route component shows 'Totoal' Fix: Replace 'Totoal' with 'Total' Result: On hover, route component shows 'Total'
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 12:50:08 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
screenshot none

Description Libor Fuka 2016-11-07 08:39:04 UTC 
Description of problem:
Typo in Route diagram in openshift-jvm console


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

Steps to Reproduce:
1. Deploy some camel route to OCP (for example s2i-springboot-camel-amq)
2. Open Java console from pod page
3. Camel tab -> jms-cbr-route -> Route Diagram
4. Hover on 'route-choose-country'
5. You can see typo totoal

Expected results:
fix typo totoal to total

Additional info:
Comment 1 Alexandre Kieling 2016-11-09 18:22:58 UTC 
Fix ready for testing. Please use openshift-jvm v1.0.51
Comment 2 Troy Dawson 2016-11-11 20:41:21 UTC 
This has been merged into ocp and is in OCP v3.4.0.25 or newer.
Comment 4 Peng Li 2016-11-15 08:41:33 UTC 
verified with OpenShift v3.4.0.25+1f36858
check the screenshot
Comment 5 Peng Li 2016-11-15 08:42:03 UTC 
Created attachment 1220759 [details]
screenshot
Comment 7 errata-xmlrpc 2017-01-18 12:50:08 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0066