[Marketen]

Problem

On a real Ubuntu 26.04 install (ASUS NUC 15), the first-boot test finished, but its single Press enter to continue prompt was buried under systemd status lines (Job rc-local.service/start running (10min / no limit)) and cloud-init output. The install looked stuck, and it wasn't clear whether Enter was needed or a reboot was safe.

Fix

dappnode_test_install.sh now repeats the result every 30 s until someone answers:

Test completed successfully.
Press Enter to continue, or reboot the machine (e.g. sudo reboot) to start DAppNode.

• Rebooting instead of pressing Enter was already safe: the test removes .firstboot before prompting, so the next boot starts DAppNode. The prompt now says so.
• Enter, or EOF on stdin, ends the wait immediately; only a timeout repeats the prompt.
• No other behavior changes. The result line is still logged to logs/dappnode_test_install.log, which the E2E checks.

Verification

• Ran the wait loop under bash 5.2 (Debian trixie): it repeats on each timeout, stops on Enter, and stops on EOF instead of spinning.
• The ISO E2E on this PR runs the full first boot, including the Enter keypress.

🤖 Generated with Claude Code