-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 6.3.0
-
Component/s: Support tools, Upgrade
-
None
-
3
-
Severity 3 - Minor
-
4
Issue Summary
After upgrade to 6.3.0 clustering page doesn't display Load,Memory or Uptime statistics
Steps to Reproduce
- Install Crowd DC
- Go to Clustering page
Expected Results
The page should show all the details related to nodes

Actual Results

The below exception(Uncaught ReferenceError) is thrown on the console logs in the browser on runtime-info-supplier-view.js
Uncaught ReferenceError: _ is not defined at com.atlassian.cluster.monitoring.cluster-monitoring-plugin:views.js?locale=en-US:31:349 at fn.zt (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:246:12408) at n.forEach (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566:622) at n.render (com.atlassian.cluster.monitoring.cluster-monitoring-plugin:views.js?locale=en-US:31:329) at m (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566:3738) at p (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566:3528) at c (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566:1384) at u.trigger (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566:3408) at n.render (com.atlassian.cluster.monitoring.cluster-monitoring-plugin:views.js?locale=en-US:7:312) at m (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566:3856) (anonymous) @ com.atlassian.cluster.monitoring.cluster-monitoring-plugin:views.js?locale=en-US:31 zt @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:246 (anonymous) @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 render @ com.atlassian.cluster.monitoring.cluster-monitoring-plugin:views.js?locale=en-US:31 m @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 p @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 c @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 u.trigger @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 render @ com.atlassian.cluster.monitoring.cluster-monitoring-plugin:views.js?locale=en-US:7 m @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 p @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 c @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 u.trigger @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 i.success @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 i @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:37 fireWith @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:37 u @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:57 (anonymous) @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:57Understand this error 2com.atlassian.cluster.monitoring.cluster-monitoring-plugin:views.js?locale=en-US:15 Uncaught ReferenceError: _ is not defined at success (com.atlassian.cluster.monitoring.cluster-monitoring-plugin:views.js?locale=en-US:15:22) at i.success (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566:6413) at i (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:37:22860) at Object.fireWith [as resolveWith] (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:37:23641) at u (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:57:30468) at XMLHttpRequest.<anonymous> (batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:57:34026) success @ com.atlassian.cluster.monitoring.cluster-monitoring-plugin:views.js?locale=en-US:15 i.success @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:2566 i @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:37 fireWith @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:37 u @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:57 (anonymous) @ batch.js?locale=en-US&plugins.jquery.migrate.load.disabled=false:57Understand this error
Workaround
No workaround currently available