Worker PXE-boots after workflow is done

[iaguis]

Currently, when a workflow is done and the user reboots, workers PXE-boot again to OSIE unless you manually set boot to disk. I tested this installing Flatcar on Packet following the tinkerbell.org tutorial.

It'd be great if there's a way to tell the worker to not PXE-boot after a workflow is done.

[alexellis]

👍 - at the least, it would make a good addition to the notes to describe how the system currently works. I think it might be a confusing experience for new users otherwise.

Short-term: note in docs?
Medium-term: CLI example for Packet's IPMI interface to change boot order?
Longer-term: feature?

[Cbkhare]

I tried to replicate this issue.

With the implementation of tinkerbell/smee#35, until there is no active workflow, PXE-boot won't happen. On replicating I found, it gets blocked before PXE step. I also tested it with worker and workflow to install Ubuntu OS. On reboot, ubuntu is brought up and pxe-boot doesn't happen.

@iaguis / @alexellis, let me know your views on it.

[gianarb]

@DailyAlice wrote documentation for the workflow execution that I hope will clarify a bit this behavior
https://github.com/tinkerbell/tinkerbell.org/pull/110/files

Tinkerbell does not do any magic action. The worker has to be configured to start from disk otherwise if an operating system is not found it will follow the boot chain going to network boot (PXE).

If your behavior looks not in line with this and it sounds like a bug please open a new issue with a workflow that we can test.

Thanks a lot