Skip to content

software/rapid-cdn: keep instancenode.cfg present across master reprocess

Fixes the random test_ssl_ca_crt failure (test result 20260703-167BE1FBB/63, note 267216):

T-0[default]: Promise 'check-cdn-instance-node-cron.py' failed with output:
  'Config file does not exist: .../T-0/etc/instancenode.cfg'

templates/instancenode.cfg.in read ${slap-configuration:configuration.dns-nameserver}. slapos.recipe.template renders at section creation, so [cdn-instance-node] depends on slap-configuration, whose timestamp changes on every bang. buildout folds a dependency's values into the section signature, so every bang reinstalls [cdn-instance-node]: etc/instancenode.cfg is deleted at the start of the run and rewritten near the end. The once-a-minute cdninstancenode cron hits that gap, fails with "Config file does not exist", and the next slapos node instance sees the promise red.

test_ssl_ca_crt triggers it because its second waitForInstance runs right after runCDNInstanceNode bangs the master.

Fix: render dns-nameserver into [cdn-requester-configuration] and reference that. Same file content, stable signature, no delete/rewrite.

Edited by Cédric Le Ninivin

Merge request reports