Last modified: 2014-05-06 18:34:14 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T66964, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 64964 - Monitor Puppet "stability"
Monitor Puppet "stability"
Status: NEW
Product: Wikimedia Labs
Classification: Unclassified
Infrastructure (Other open bugs)
unspecified
All All
: Unprioritized enhancement
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-05-06 18:34 UTC by Tim Landscheidt
Modified: 2014-05-06 18:34 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Tim Landscheidt 2014-05-06 18:34:14 UTC 
At the moment, Puppet status in [[wikitech:Special:NovaInstance]] is either "unknown", "ok" (last Puppet run succeeded), "stale" (last Puppet run was successful, but long ago), or "failed" (last Puppet run failed).

However this doesn't catch situations like bug #64216 where a service is started on every Puppet run but never stays alive, i. e. the Puppet runs are technically successful, but fail on a "semantic" level.

So it would be nice to monitor that for example (given the rate of changes in operations/puppet at the moment) in a 24-hour period, there is at least one Puppet run that was successful, but didn't change anything as an indicator that Puppet is "stable".
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links