-
Bug
-
Resolution: Fixed
-
Minor
-
None
We run multiple Jenkins installations. At least 3 of them meanwhile show N+1 in the admin warnings bubble at the top, when there are actually N admin warnings. Is there any way to "reset" that counter?
A typical example is this one: The bubble shows "2", but there is only 1 warning: 
Or might there be an actual admin warning that is just "invisible"? And if so, where or how could I check for that?
[JENKINS-71198] Admin warnings counter too high
Michael Keppler
created issue -
Michael Keppler
made changes -
| Comment |
[ For one of the affected installations I know that it had to be reverted to an older weekly version because it was affected by a bug that crashed it during startup. I'm sure there was an admin warning active in the newer version before the revert to the older version. I'm not sure if such a "warning from the future" could cause such an effect.
For the other 2 systems I don't know the history of their installation and upgrades well enough to come up with a guess. Is there anything I can do to "recalculate" the counter, or to check something on disk? I don't have access to that machine for anything like remote-debugging, but I could read any file from its file system, if that helps. BTW: I'm still not sure if the number in the header is wrong, or if there is some kind of rendering issue in the actual displaying of the warnings that would lead to making the warning invisible or suppress it from rendering. ] |
Michael Keppler
made changes -
| Attachment | New: image-2023-05-07-21-43-37-688.png [ 60379 ] |
I now know this is a monitor of type https://github.com/jenkinsci/spotinst-plugin/blob/master/src/main/java/hudson/plugins/spotinst/cloud/monitor/SpotinstCloudsCommunicationMonitor.java which renders as empty list in the list (that means the number in the header is correct). The html source for the monitors popup looks like this:
That empty list item is rendered here: https://github.com/jenkinsci/jenkins/blob/71d1df44f19d12887cad41d92c0973a8148eefb7/core/src/main/resources/jenkins/management/AdministrativeMonitorsApiData/monitorsList.jelly using the monitor object. I haven't understood how I can debug to the included message.jelly page there. The dump of the monitor object looks like:
<hudson.plugins.spotinst.cloud.monitor.SpotinstCloudsCommunicationMonitor@71be5baa spotinstCloudsCommunicationFailures=null spotinstCloudsCommunicationInitializing=null id=hudson.plugins.spotinst.cloud.monitor.SpotinstCloudsCommunicationMonitor>
Any more advice for debugging the rendering of the message.jelly part or should I just forward the issue as is to the Spotinst plugin maintainers?
Michael Keppler
added a comment - - edited I now know this is a monitor of type https://github.com/jenkinsci/spotinst-plugin/blob/master/src/main/java/hudson/plugins/spotinst/cloud/monitor/SpotinstCloudsCommunicationMonitor.java which renders as empty list in the list (that means the number in the header is correct). The html source for the monitors popup looks like this:
That empty list item is rendered here: https://github.com/jenkinsci/jenkins/blob/71d1df44f19d12887cad41d92c0973a8148eefb7/core/src/main/resources/jenkins/management/AdministrativeMonitorsApiData/monitorsList.jelly using the monitor object. I haven't understood how I can debug to the included message.jelly page there. The dump of the monitor object looks like:
<hudson.plugins.spotinst.cloud.monitor.SpotinstCloudsCommunicationMonitor@71be5baa spotinstCloudsCommunicationFailures=null spotinstCloudsCommunicationInitializing=null id=hudson.plugins.spotinst.cloud.monitor.SpotinstCloudsCommunicationMonitor>
Any more advice for debugging the rendering of the message.jelly part or should I just forward the issue as is to the Spotinst plugin maintainers? 
Markus Winter
made changes -
| Component/s | New: spotinst-plugin [ 21520 ] |
Michael Keppler
added a comment - Fixed in https://github.com/jenkinsci/spotinst-plugin/pull/98. Released with spotinst-plugin 2.2.15.
Michael Keppler
added a comment - Fixed in https://github.com/jenkinsci/spotinst-plugin/pull/98. Released with spotinst-plugin 2.2.15. Michael Keppler
made changes -
| Released As | New: https://github.com/jenkinsci/spotinst-plugin/releases/tag/spotinst-2.2.15 | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Any further hints on the differences between the two systems?
I have never seen that behavior on any of the LTS or weekly systems that I use regularly.