Agent fails to boot on Noble Numbat pre-release stemcells
Closed this issue · 0 comments
cunnie commented
Jammy uses the Ubuntu package resolveconf for manipulating DNS resolution order; however, that package has been deprecated in Noble Numbat in favor of systemd-resolved. The packages function differently, and the result is that the Agent restarts every time it attempts to set up networking.
We need to address this failure by having the Agent determine which sort of DNS resolution manipulation is necessary, and accommodate the appropriate system (resolveconf vs. systemd-resolved).
Work is currently on https://github.com/cloudfoundry/bosh-agent/tree/noble-systemd-resolved
Fixes the following BOSH Agent failure (from current):
2024-02-09_22:52:36.54320 [File System] 2024/02/09 22:52:36 DEBUG - Reading file /etc/resolv.conf
2024-02-09_22:52:36.54321 [main] 2024/02/09 22:52:36 ERROR - App setup Running bootstrap: Setting up networking: validating dns configuration: Reading /etc/resolv.conf: Opening file /etc/resolv.conf: open /etc/resolv.conf: no such file or directory
2024-02-09_22:52:36.54321 [main] 2024/02/09 22:52:36 ERROR - Agent exited with error: Running bootstrap: Setting up networking: Validating dns configuration: Reading /etc/resolv.conf: Opening file /etc/resolv.conf: open /etc/resolv.conf: no such file or directory