Page MenuHomePhabricator

Instances with Puppet failures
Closed, ResolvedPublic

Description

Notify project owners about these failures:

main:

  • Glampipe.glampipe.eqiad.wmflabs
  • abogott-horizon.testlabs.eqiad.wmflabs
  • abogott-scapserver.testlabs.eqiad.wmflabs
  • deployment-maps05.deployment-prep.eqiad.wmflabs
  • deployment-ms-be03.deployment-prep.eqiad.wmflabs
  • deployment-ms-be04.deployment-prep.eqiad.wmflabs
  • deployment-ms-fe02.deployment-prep.eqiad.wmflabs
  • swift-stretch-ms-fe01.swift.eqiad.wmflabs
  • tools-elastic-01.tools.eqiad.wmflabs (puppetmaster got switched?)
  • tools-elastic-03.tools.eqiad.wmflabs (puppetmaster got switched?)
  • tools-logs-02.tools.eqiad.wmflabs (puppetmaster got switched?)
  • tools-paws-master-01.tools.eqiad.wmflabs (puppetmaster got switched?)
  • toolsbeta-sgegrid-master.toolsbeta.eqiad.wmflabs

eqiad1:

  • Argon.codereview.eqiad.wmflabs
  • Radon.codereview.eqiad.wmflabs
  • af-debmonitor.automation-framework.eqiad.wmflabs
  • af-puppetdb01.automation-framework.eqiad.wmflabs
  • af-puppetdb02.automation-framework.eqiad.wmflabs
  • af-puppetmaster02.automation-framework.eqiad.wmflabs
  • filippo-log-jessie01.logging.eqiad.wmflabs
  • gtirloni-stretch-01.testlabs.eqiad.wmflabs
  • mc-clusterA-1.test-twemproxy.eqiad.wmflabs
  • mc-clusterA-2.test-twemproxy.eqiad.wmflabs
  • mc-clusterB-1.test-twemproxy.eqiad.wmflabs
  • mc-clusterB-2.test-twemproxy.eqiad.wmflabs
  • puppenmeister.planet.eqiad.wmflabs
  • striker-deploy03.striker.eqiad.wmflabs (Trusty bug, see T201331)
  • traffic-recdns-anycast.traffic.eqiad.wmflabs

Event Timeline

Krenair renamed this task from tools: Instances with Puppet failures to Instances with Puppet failures.Nov 6 2018, 7:34 PM
Krenair edited projects, added Cloud-VPS, Tracking-Neverending; removed Toolforge.
Krenair subscribed.
GTirloni updated the task description. (Show Details)

Because project owners have different priorities and reasons for having Puppet broken, I'm considering the notifications as the task being done, so this task doesn't stay open for an indefinite amount of time.

We can track the individual cases through the subtasks, if that's okay.