I took care of this by revising the following patch in deployment-puppetserver-1.deployment-prep:/srv/git/operations/puppet : --- [BETA HACK] Changes to profile::puppetserver::volatile
This allows a stubbed-out version of this class to apply on a deployment-prep puppetserver. Probably better than hunting down every use of this elsewhere. Change-Id: Ie8da6b896b26f03d0dbc15160ee4f6884acc8980 On Fri, Oct 3, 2025 at 8:03 AM <[email protected]> wrote: > 1 alert for alertname=PuppetSyncFailure project=deployment-prep > View in Alertmanager > <http://metricsinfra-alertmanager-2:9093/#/alerts?receiver=deployment-prep_betacluster> > *[1] Firing* > *Labels* > alertname = PuppetSyncFailure > instance = deployment-puppetserver-1 > job = node > project = deployment-prep > repository = /srv/git/operations/puppet > severity = warning > *Annotations* > summary = Failed to update Puppet repository /srv/git/operations/puppet on > instance deployment-puppetserver-1 in project deployment-prep > Source > <https://prometheus.wmcloud.org/graph?g0.expr=puppet_sync_upstream_rebase_success+%21%3D+1&g0.tab=1> > Sent by Alertmanager <http://metricsinfra-alertmanager-2:9093> > _______________________________________________ > Betacluster-alerts mailing list -- [email protected] > To unsubscribe send an email to > [email protected] >
_______________________________________________ Betacluster-alerts mailing list -- [email protected] To unsubscribe send an email to [email protected]
