Skip to content

Support device restart or kexec as part of workflows #29

Open
@chrisdoherty4

Description

@chrisdoherty4

Summary

When provisioning devices users inevitably need to restart the device (or kexec). To date, users achieve a restart through an action which can lead to incorrect status reporting on Workflows.

When the restart action is run it instructs the kernel to perform a system restart. The restart process races against the action exiting and Tink Worker reporting the action was successful. In the case of kexec, we rarely - if ever - see the action transition to a success state. This generally leaves workflows to timeout which is misleading for users.

This issue is to track the introduction of restart/kexec to workflows as a built in feature removing the need to include an action. Other proposals are welcome.

Metadata

Metadata

Assignees

No one assigned

    Labels

    status/acceptedThe scope and kind of work is agreed and the item accepted to the backlogtheme/featureNew functionality in Tinkerbell

    Type

    No type

    Projects

    Status

    Accepted

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions