What I expected to happen:settings-committer is run before sundog, pluto, and thar-be-settings to commit any new settings in the launch transaction. It should tolerate an empty transaction since there won't always be new settings to generate, especially on a reboot.
What actually happened:
System failed to reboot with this error:
[ 9.329884] Starting User-specified setting generators...
[ 9.441691] settings-committer[1141]: Error sending POST to /tx/commit?tx=bottlerocket-launch: Tried to commit with no pending changes
[FAILED] Failed to start User-specified setting generators.
How to reproduce the problem:
Launch an aws-k8s-* node and reboot.
Image I'm using:
aws-k8s-1.28-nvidia
What I expected to happen:
settings-committer
is run beforesundog
,pluto
, andthar-be-settings
to commit any new settings in the launch transaction. It should tolerate an empty transaction since there won't always be new settings to generate, especially on a reboot.What actually happened: System failed to reboot with this error:
How to reproduce the problem: Launch an
aws-k8s-*
node and reboot.