[Bug]: dnsmasq ConfigMap `server=` directive resets to empty after Holorouter reboot

[hirohiro43]

Holorouter Version

9.0.2

VCF Version

VCF 9.0.2.0

Target Type

vCenter Cluster

Describe the bug

After rebooting the Holorouter VM, the server= directive in
/holodeck-runtime/dnsmasq/dnsmasq_configmap.yaml loses its upstream DNS value and
becomes empty (server=), causing DNS resolution to fail inside the Holodeck environment.

Inspecting the ConfigMap after reboot:
root@holorouter [ ~ ]# cat /holodeck-runtime/dnsmasq/dnsmasq_configmap.yaml
...
server=
...

Reproduction steps

1.Reboot the Holorouter VM (shutdown -r now)

2.After reboot, observe that DNS resolution fails for internal/external FQDNs

3.SSH into Holorouter and inspect the ConfigMap:
cat /holodeck-runtime/dnsmasq/dnsmasq_configmap.yaml
server=

Expected behavior

The server= directive in the dnsmasq ConfigMap should retain its configured upstream DNS
server value (e.g., 8.8.8.8) across Holorouter reboots.

After Holorouter reboot, the server= value is cleared. dnsmasq pod continues running but
cannot resolve external names, causing deployment failures or connectivity issues.

Workaround

Manually restore the server= value and reapply the ConfigMap:

sudo vi /holodeck-runtime/dnsmasq/dnsmasq_configmap.yaml
# Set: server=8.8.8.8

kubectl apply -f /holodeck-runtime/dnsmasq/dnsmasq_configmap.yaml

Relevant logs

Additional context

No response