Bug 1380392 - openshift-jvm A-MQ console "Browse" doesn't show any messages
Summary: openshift-jvm A-MQ console "Browse" doesn't show any messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.3.1
Assignee: Alexandre Kieling
QA Contact: Xia Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-29 12:58 UTC by Marek Schmidt
Modified: 2018-07-19 03:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Missing HawtIO UI data table configuration option Consequence: Data table component would not show up Fix: Added the primary key configuration option Result: Data table component started to appear
Clone Of:
Environment:
Last Closed: 2016-10-27 15:42:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2084 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.3.1.3 bug fix update 2016-10-27 19:41:25 UTC

Description Marek Schmidt 2016-09-29 12:58:56 UTC
Description of problem:

The list of messages in the "Browse" tab in the A-MQ console is empty, with the following javascript error in the borwser logs:

libs-3d3f8220c5.js:5 Error: Missing primary key. Please add a property called 'id', '_id', '_key', or 'name' to your entities. Alternatively, set the 'primaryKeyFn' configuration option.
    at h (https://ose3-master.192.168.122.5.xip.io:8443/console/java/libs-3d3f8220c5.js:44:29003)
    at https://ose3-master.192.168.122.5.xip.io:8443/console/java/libs-3d3f8220c5.js:44:29981
    at Array.forEach (native)
    at y (https://ose3-master.192.168.122.5.xip.io:8443/console/java/libs-3d3f8220c5.js:44:29953)
    at f.$broadcast (https://ose3-master.192.168.122.5.xip.io:8443/console/java/libs-3d3f8220c5.js:6:4777)
    at f.l.sortBy (https://ose3-master.192.168.122.5.xip.io:8443/console/java/libs-3d3f8220c5.js:44:30996)
    at fn (eval at compile (https://ose3-master.192.168.122.5.xip.io:8443/console/java/libs-3d3f8220c5.js:7:20695), <anonymous>:4:230)
    at t (https://ose3-master.192.168.122.5.xip.io:8443/console/java/libs-3d3f8220c5.js:5:25276)
    at r (https://ose3-master.192.168.122.5.xip.io:8443/console/java/libs-3d3f8220c5.js:8:9016)
    at f.$eval (https://ose3-master.192.168.122.5.xip.io:8443/console/java/libs-3d3f8220c5.js:6:3391)(anonymous function) @ libs-3d3f8220c5.js:5

Version-Release number of selected component (if applicable):
openshift v3.3.0.32
kubernetes v1.3.0+52492b4
openshift-jvm Version: 1.0.47 Commit ID: fe68cabf7eb0f96c13dedbf56fae43b0248323d4

How reproducible:

Always (tried Firefox and Google Chrome)

Steps to Reproduce:
1. deploy amq62-basic template, fill MQ_USERNAME / MQ_PASSWORD as "admin" / "admin"
2. click on the "Open Java Console" link in the pod detail view
3. open the ActiveMQ tab
4. click on "Queue" item in the tree on the left and "+ Create"
5. create a queue named "foobar"
6. click on the "foobar" queue in the tree
7. click "Send"
8. Note the warning about amq password, follow the link and set "admin" / "admin" MQ username/password
9. go back to send, send a few plaintext messages
10. Click Browse

Actual results:

Notice no messages are shown. A JavaScript error is shown in the browser logs.

Expected results:

All our sent messages should be listed.

Additional info:

Comment 1 Alexandre Kieling 2016-10-05 15:10:35 UTC
Fixed version: v1.0.48

Comment 2 Jessica Forrester 2016-10-05 15:13:22 UTC
This can't go to MODIFIED until origin-web-console/enterprise-3.3 branch is updated to pull in v1.0.48

Comment 3 Jessica Forrester 2016-10-05 15:28:26 UTC
Vendor into origin-web-console/enterprise-3.3 is started here https://github.com/openshift/origin-web-console/pull/626

Comment 4 Alexandre Kieling 2016-10-05 20:22:11 UTC
A new version with only the bug fixes has been released: v1.0.49

Comment 6 Xia Zhao 2016-10-14 12:06:45 UTC
Checked against 

# openshift version
openshift v3.3.1.1
kubernetes v1.3.0+52492b4
etcd 2.3.0+git

The fix for this bug seems not merged in yet, and the bug is still reproduced. Need a new build containing the fix to verify the bug.

@yapei @yanpzhan please share test env with us if you have.

Comment 8 Peng Li 2016-10-17 05:46:52 UTC
verified on below version[1] and use Firefox, could successfully get the messages[2].

[1]
[root@qe-penli-master-1 ~]# openshift version
openshift v3.3.1.2
kubernetes v1.3.0+52492b4
etcd 2.3.0+git

[2]
Message ID
ID:broker-amq-1-q4z0w-36480-1476682647710-11:1:1:1:1
ID:broker-amq-1-q4z0w-36480-1476682647710-7:1:1:1:1
ID:broker-amq-1-q4z0w-36480-1476682647710-9:1:1:1:1

Comment 10 errata-xmlrpc 2016-10-27 15:42:38 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-2016:2084


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