Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Not A Defect
-
core 2.289.1.2; monitoring:1.87.0 and monitoring:1.88.0; metrics:4.0.2.7
and other assorted plugins.
Description
Beginning with upgrade to 2.289.1.2 we noticed that loadStatistics for labels and agents is now borked.
E.g. /label/VALIDLABEL/load-statistics shows a broken icon for the statistics, while
/label/VALIDLABEL/loadStatistics/graph?type=min&width=1295&height=500
Shows an OOPS demon jenkins with an error.
However `label/VALIDLABEL/api/python?pretty=true&depth=3` does provide the expected values.
See attached screenshots.
We also recently removed several plugins as suggested by the Jenkins Health Advisor (tables-to-div issues as well as obsolete plugins).
We make use of these statistics to help understand loads on our agents - usually by LABEL.
Load-statistics are similarly broken for agents, too, e.g.
`/computer/VALIDAGENTNAME/load-statistics` is similarly broken.
Since we had recently upgraded the monitoring plugin, we downgraded that and restarted but no help there.
Attachments
Activity
Thanks for the report. I was worried that the fix for JENKINS-65336 that was included in https://github.com/jenkinsci/jenkins/pull/5408 as part of Jenkins 2.289.1 might be a cause of the problem, but I don't see the problem with Jenkins 2.289.2 and I didn't see the problem with 2.289.1.
Steven Christenson
added a comment - Digging into the logs, this stands out:
java.lang.NoClassDefFoundError: Could not initialize class org.jfree.chart.JFreeChart
However I'm just floundering around in Kibana looking at logs from a dozen different jenkins servers... But this was close in time to the exception thrown.
And of course, I'm producing this problem in a Cloudbees Jenkins Enterprise solution, not the OSS solution... so perhaps it's something specific to Cloudbees.
Steven Christenson
added a comment - Digging into the logs, this stands out:
java.lang.NoClassDefFoundError: Could not initialize class org.jfree.chart.JFreeChart
However I'm just floundering around in Kibana looking at logs from a dozen different jenkins servers... But this was close in time to the exception thrown.
And of course, I'm producing this problem in a Cloudbees Jenkins Enterprise solution, not the OSS solution... so perhaps it's something specific to Cloudbees. It works fine on 2.289.3,
Please re-produce with Jenkins itself and not the cloudbees offering
It's probably worth noting that the "Load Statistics" selection for labels or agents maps to "load-statistics" in the URL but the api is loadStatistics. This doesn't seem to be different from before, but the inconsistent mappings are "interesting".