Page MenuHomePhabricator

deployment-acme-chief0{5,6} puppet failures for 'profile::opensearch::cirrus::enable_remote_search'
Closed, ResolvedPublicBUG REPORT

Description

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Function lookup() did not find a value for the name 'profile::opensearch::cirrus::enable_remote_search' (file: /srv/puppet_code/environments/production/modules/profile/manifests/opensearch/cirrus/server.pp, line: 9) on node deployment-acme-chief06.deployment-prep.eqiad1.wikimedia.cloud

Event Timeline

This looks like something random happened to the Horizon managed puppet config. It doesn't make any sense why role::cirrus::beta is being applied for the deployment-acme-chief prefix.

Looks like an accident by @bking while working on T389971: Migrate deployment-prep elasticsearch cluster to opensearch: https://gerrit.wikimedia.org/r/plugins/gitiles/cloud/instance-puppet/+/1ef9174ec5b765cf1b1251068896a870af1345ba

The deployment-acme-chief prefix puppet is the first in the list, and I think I remember that a reload on https://horizon.wikimedia.org/project/prefixpuppet/ puts you in the first prefix no matter where you were before.

Mentioned in SAL (#wikimedia-releng) [2025-03-27T00:55:34Z] <bd808> Removed prefix puppet classes for deployment-acme-chief (T390128)

I moved role::acme_chief::cloud from instance level puppet config to the deployment-acme-chief prefix too. This may help folks notice when they land on that config unexpectedly.

bd808 claimed this task.