You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Apply Talos fails to apply the files due to it missing the operation key, logically, and throws the Talos System in a bootloop.
Expected Behavior
There are a few things that could've happened, and one of them should've happened, that should prevent the scope of this issue:
A. Validate the file patches to be at-least valid patches
B. If a patch fails, dont try to reapply an already know borking file-patch and keep rebooting
C. revert the Apply if a fifepatch is broken
However, none of these options happen.
So we end up with a broken system instead.
Logs
Environment
Talos version: 1.8.1
Kubernetes version: 1.31
Platform: Irrelevant
The text was updated successfully, but these errors were encountered:
The bug here is that the machine config validation is probably incomplete.
The workaround is to apply previous machine config, as apid is running, which will fix this issue
I'm aware how to reverse the issue, no worries... These are testruns/testmachines/testusers :)
I'm reporting this mostly to get it fixed more globally.
Bug Report
Description
When we add a files in a machine config like this:
notice the lacking "operation" key
On Apply Talos fails to apply the files due to it missing the operation key, logically, and throws the Talos System in a bootloop.
Expected Behavior
There are a few things that could've happened, and one of them should've happened, that should prevent the scope of this issue:
A. Validate the file patches to be at-least valid patches
B. If a patch fails, dont try to reapply an already know borking file-patch and keep rebooting
C. revert the Apply if a fifepatch is broken
However, none of these options happen.
So we end up with a broken system instead.
Logs
Environment
The text was updated successfully, but these errors were encountered: