Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1392376 - openshift-jvm Camel Source: update
openshift-jvm Camel Source: update
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.3.1
Unspecified Linux
unspecified Severity low
: ---
: ---
Assigned To: Alexandre Kieling
Peng Li
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2016-11-07 06:18 EST by Libor Fuka
Modified: 2017-03-08 13 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: JavaScript bug Consequence: message does not change after Camel route source update Fix: Fix JavaScript bug Result: message changes after Camel route source update
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-18 07:50:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 12:23:26 EST

  None (edit)
Description Libor Fuka 2016-11-07 06:18:25 EST 
Description of problem:
Route component not updated in html page after route source update

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

How reproducible:
always

Steps to Reproduce:
1. Deploy some camel route to OCP (for example s2i-springboot-camel-amq: https://github.com/jboss-fuse/application-templates/blob/application-templates-2.0.fuse-000007/quickstarts/springboot-camel-amq-template.json)
2. Open Java console from pod page
3. Camel tab -> jms-cbr-route -> Source
4. Update log message <log message="Done processing MESSAGE ${file:name}" id="route-final-log"/>
5. Click Update button
6. Click route-final-log -> message does not include MESSAGE

Actual results:
message does not include MESSAGE after jms-cbr-route source update

Expected results:
message includes MESSAGE after jms-cbr-route source update

Additional info:
Comment 1 Alexandre Kieling 2016-11-09 13:22:10 EST 
Fix ready for testing. Please use openshift-jvm v1.0.51
Comment 2 Troy Dawson 2016-11-11 15:41:52 EST 
This has been merged into ocp and is in OCP v3.4.0.25 or newer.
Comment 4 Peng Li 2016-11-16 22:39:56 EST 
verified, updated message could reflect.

openshift v3.4.0.26+f7e109e
openshift-jvm Version: 1.0.52
Comment 6 errata-xmlrpc 2017-01-18 07:50:25 EST 
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
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.