The 'powerState' status of kubernetes object 'machine' not being updated after changing machine powerstate

[haiwu]

The 'powerState' status of kubernetes object 'machine' not being updated, after the machine has been powered on/off via certain job yaml with tasks->powerAction being set to either 'on' or 'off'

Expected Behaviour

The particular kubernetes machine object's 'powerState' status should be in sync with machine's current power state, after it has been powered on/off via job yaml, but that's currently not the case.

Current Behaviour

No update to the machine 'powerState' status:

kubectl get machines machine-sample -n rufio-system -oyaml | yq .status.powerState

Possible Solution

Ignore this status field for now.

Steps to Reproduce (for bugs)

For example, say this machine-sample was with powerstate being 'on' before, then we applying a new job yaml with tasks -> powerAction setting to 'off', the host will be powered off correctly via this new job’s task, but the following machine’s .status.powerState still stay showing up as being 'on' instead of 'off' :
kubectl get machines machine-sample -n rufio-system -oyaml | yq .status.powerState

Context

Would be helpful to get this one right later.

Your Environment

kind cluster with just Rufio installed via its doc here: 'https://github.com/tinkerbell/rufio/blob/main/docs/README.md'

• Operating System and version (e.g. Linux, Windows, MacOS): Linux

• How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details: Tinkerbell not installed for this quick test environment just for Rufio

• Link to your project or a code example to reproduce issue: Just follow steps in 'https://github.com/tinkerbell/rufio/blob/main/docs/README.md' to setup a new kind cluster first..