Ticket #3213 (closed enhancement: Fixed)

Opened 8 months ago

Last modified 3 months ago

Add a commit() to UpdateCheck to make sure dmd.lastVersionCheckDate gets updated

Reported by: jstevens Owned by: jstevens
Priority: 3 - Medium Milestone: zenoss-2.3
Component: All Version: 2.2.0
Keywords: zenoss-2.2.1-verified Cc:
Community Patch Attached: Deployed @ Customer:
Installer: Maintenance Target:
Specific ZenPack: Maintenance Status:
Documentation Note?: Not required Regression:

Description

We have quite a few installs of zenoss that are checking their version number very frequently, as much as once a minute in some cases. This might be because the sendEvent in UpdateCheck.check() (or something near it in the code) is throwing an exception and keeping the dmd.lastVersionCheckAttempt setting from being committed.

If it is not a manual check, ie if this is zenactions checking, then commit immediately after setting dmd.lastVersionCheckAttempt to make sure that gets stored and the version isn't checked for another day.

Change History

Changed 8 months ago by jstevens

  • status changed from new to closed
  • resolution set to fixed

(In [9330]) fixes #3213

  • making sure dmd.lastVersionCheckAttempt gets committed when we do an update check.

Changed 7 months ago by jstevens

  • keywords zenoss-2.2.1-approved added; zenoss-2.2.1-proposed removed

This was reviewed by ead when originally made.

Changed 7 months ago by ecn

  • milestone set to zenoss-2.3

Changed 7 months ago by ian

(In [9419]) * Refs #3213: Backported r9330 into the zenoss-2.2.x branch

Changed 7 months ago by ian

  • keywords zenoss-2.2.1-patched added; zenoss-2.2.1-approved removed

Changed 6 months ago by ecn

  • keywords zenoss-2.2.1-verified added; zenoss-2.2.1-patched removed

cent5 32-bit native rpm build 24

Changed 3 months ago by bbibeault

  • reviewed set to 1
Note: See TracTickets for help on using tickets.