Investigate
Description
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| wmcs.postrgesql.osm_primary: add missing required engine param | operations/puppet | production | +22 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | dancy | T302086 Set scap minimum python version to 3.7 | |||
| Resolved | None | T247045 Migrate all of production metal and VMs to Buster or later | |||
| Resolved | hnowlan | T264292 Migrate maps to Buster | |||
| Resolved | BUG REPORT | None | T312751 Geoline never shows up after OSM and Wikidata entries have been updated | ||
| Resolved | None | T260456 [Maps] Reduce Map Sync Latency with OpenStreetMaps (OSM) | |||
| Resolved | hnowlan | T269582 [OSM] perform imposm3 migration in production | |||
| Resolved | dcaro | T276039 Puppet failure on clouddb1003.clouddb-services.eqiad.wmflabs |
Event Timeline
Actual error:
dcaro@clouddb1003:~$ sudo run-puppet-agent Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Loading facts Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Osm::Planet_sync[gis]: expects a value for parameter 'engine' (file: /etc/puppet/modules/profile/manifests/wmcs/services/postgres/osm_primary.pp, line: 32) on node clouddb1003.clouddb-services.eqiad.wmflabs Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run
Yes, the change that introduced the error is https://gerrit.wikimedia.org/r/c/operations/puppet/+/644482
Adding a new parameter engine.
@MSantos hi, the change https://gerrit.wikimedia.org/r/c/operations/puppet/+/644482, added a new engine required parameter that our manifests (profile/manifests/wmcs/services/postgres/osm_primary.pp) are not passing and no default or updates on our manifests were made.
Can you guide me on what and where should I change to adapt to it? (should I hardcode the engine name on our module? Add a default? Is there anything else needed?).
Thanks!
I didn't realise this module was used outside of the maps profile, apologies. You can add engine => "osm2pgsql" as a parameter to osm::planet_sync to restore the previous behaviour.
Ack thanks! I'll try to add a dummy test so it explodes before and we catch it in review :)
Change 667560 had a related patch set uploaded (by David Caro; owner: David Caro):
[operations/puppet@production] wmcs.postrgesql.osm_primary: add missing required engine param
Change 667560 merged by David Caro:
[operations/puppet@production] wmcs.postrgesql.osm_primary: add missing required engine param