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

          Mark Waite added a comment -

          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.

          Mark Waite added a comment - 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.

          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?

          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?

          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.

            Unassigned Unassigned
            bananeweizen Michael Keppler
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: