Page MenuHomePhabricator

[Cloud VPS alert][admin] Puppet failure on buildvm-f575acf4-c566-4258-9a5f-20b9ec80ccad.admin.eqiad1.wikimedia.cloud (172.16.4.109)
Closed, ResolvedPublic

Description

Write the description below

From email:

Date: Fri, 20 Aug 2021 08:15:06 +0000
From: root <root@buildvm-f575acf4-c566-4258-9a5f-20b9ec80ccad.admin.eqiad1.wikimedia.cloud>
To: dcaro@wikimedia.org
Subject: [Cloud VPS alert][admin] Puppet failure on buildvm-f575acf4-c566-4258-9a5f-20b9ec80ccad.admin.eqiad1.wikimedia.cloud (172.16.4.109)


Puppet is having issues on the "buildvm-f575acf4-c566-4258-9a5f-20b9ec80ccad.admin.eqiad1.wikimedia.cloud (172.16.4.109)" instance in project
admin in Wikimedia Cloud VPS.

Puppet did not run in the last 413824.74447512627, though the last run was a success.

Working Puppet runs are needed to maintain instance security and logins.
As long as Puppet continues to fail, this system is in danger of becoming
unreachable.

You are receiving this email because you are listed as member for the
project that contains this instance.  Please take steps to repair
this instance or contact a Cloud VPS admin for assistance.

You might find some help here:
    https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/Runbooks/Cloud_VPS_alert_Puppet_failure_on

For further support, visit #wikimedia-cloud on libera.chat or
<https://wikitech.wikimedia.org>

Some extra info follows:
---- Last run summary:
changes:
  total: 0
events:
  failure: 0
  success: 0
  total: 0
resources:
  changed: 0
  corrective_change: 0
  failed: 0
  failed_to_restart: 0
  out_of_sync: 0
  restarted: 0
  scheduled: 0
  skipped: 0
  total: 0
time:
  fact_generation: 0.24738773200078867
  last_run: 1629446525
  plugin_sync: 1.3663277269988612
  total: 2.054278645
version:
  config: null
  puppet: 5.5.22


---- Failed resources if any:

  No failed resources.

---- Exceptions that happened when running the script if any:
  No exceptions happened.

Event Timeline

dcaro triaged this task as High priority.Aug 20 2021, 8:49 AM
dcaro created this task.

This VM is used to create new images, my guess is that when booting up, the puppet state file has the timestamp when
the base image was created, thus failing the check.

Will close for now unless it becomes a frequent issue (or it bothers me enough to fix it).