Page MenuHomePhabricator

Puppet broken in the automation-framework project
Closed, ResolvedPublic

Description

"af-debmonitor.automation-framework.eqiad1.wikimedia.cloud": "WARNING: Failed to apply catalog, zero resources tracked by Puppet. Could be an interrupted request or a dependency cycle.",
"af-nb-db-1.automation-framework.eqiad1.wikimedia.cloud": "WARNING: Failed to apply catalog, zero resources tracked by Puppet. Could be an interrupted request or a dependency cycle.",
"af-puppetdb01.automation-framework.eqiad1.wikimedia.cloud": "WARNING: Failed to apply catalog, zero resources tracked by Puppet. Could be an interrupted request or a dependency cycle.",
"af-puppetdb02.automation-framework.eqiad1.wikimedia.cloud": "WARNING: Failed to apply catalog, zero resources tracked by Puppet. Could be an interrupted request or a dependency cycle.",
"af-puppetmaster02.automation-framework.eqiad1.wikimedia.cloud": "WARNING: Failed to apply catalog, zero resources tracked by Puppet. Could be an interrupted request or a dependency cycle.",

This doesn't look like code rot, there's something broken with the whole project puppet infra.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

af-puppetmaster02.automation-framework.eqiad1.wikimedia.cloud also seems to be running Debian Jessie, so anything done here will need to start with a rebuild of that host.

@crusnov af-puppetmaster02 is about to be deleted, all the other VMs in the same project that are client of this puppetmaster must be reconfigured to use the global WMCS puppetmaster or a new local puppetmaster should be created.
Are the local patches still needed?
Is a local puppetmaster still required?

Volans claimed this task.

I've deleted all the old instances that included also all the ones that had puppet broken. Sorry for the delay.