talosctl reboot --wait failing for os:operator role
#7197
Assignees
Comments
utkuozdemir
changed the title
talosctl reboot --wait=false failing for os:operator roletalosctl reboot --wait failing for os:operator role
|
We should probably look into whitelisting some paths in a safe way to |
1 task
utkuozdemir
added a commit
to utkuozdemir/talos
that referenced
this issue
May 6, 2024
If the `reboot/reset/shutdown/upgrade` action tracker cannot read the boot ID from the node under `/proc/sys/kernel/random/boot_id` due to insufficient permissions (e.g., when `talosctl reboot` is used over Omni), fall back to skipping boot ID check instead of hard-failing. Closes siderolabs#7197. Signed-off-by: Utku Ozdemir <utku.ozdemir@siderolabs.com>
utkuozdemir
added a commit
to utkuozdemir/talos
that referenced
this issue
May 6, 2024
If the `reboot/reset/shutdown/upgrade` action tracker cannot read the boot ID from the node under `/proc/sys/kernel/random/boot_id` due to insufficient permissions (e.g., when `talosctl reboot` is used over Omni), fall back to skipping boot ID check instead of hard-failing. Closes siderolabs#7197. Signed-off-by: Utku Ozdemir <utku.ozdemir@siderolabs.com>
utkuozdemir
added a commit
to utkuozdemir/talos
that referenced
this issue
May 7, 2024
If the `reboot/reset/shutdown/upgrade` action tracker cannot read the boot ID from the node under `/proc/sys/kernel/random/boot_id` due to insufficient permissions (e.g., when `talosctl reboot` is used over Omni), fall back to skipping boot ID check instead of hard-failing. Closes siderolabs#7197. Signed-off-by: Utku Ozdemir <utku.ozdemir@siderolabs.com>
smira
pushed a commit
to smira/talos
that referenced
this issue
May 17, 2024
If the `reboot/reset/shutdown/upgrade` action tracker cannot read the boot ID from the node under `/proc/sys/kernel/random/boot_id` due to insufficient permissions (e.g., when `talosctl reboot` is used over Omni), fall back to skipping boot ID check instead of hard-failing. Closes siderolabs#7197. Signed-off-by: Utku Ozdemir <utku.ozdemir@siderolabs.com> (cherry picked from commit 478b862)
smira
pushed a commit
to smira/talos
that referenced
this issue
Jul 22, 2024
If the `reboot/reset/shutdown/upgrade` action tracker cannot read the boot ID from the node under `/proc/sys/kernel/random/boot_id` due to insufficient permissions (e.g., when `talosctl reboot` is used over Omni), fall back to skipping boot ID check instead of hard-failing. Closes siderolabs#7197. Signed-off-by: Utku Ozdemir <utku.ozdemir@siderolabs.com> (cherry picked from commit 478b862)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When
--waitis used, reboot command does a/machine.MachineService/Readto read the boot ID before issuing the reboot. Since/machine.MachineService/Readis only allowed for admins, reboot only works when--wait=falseis used by non-admins.The text was updated successfully, but these errors were encountered: