-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
examples/Debian OS provisioning not working- kexec? #85
Comments
I recently came across this issue. Switching to hook, I was able to use the kexec image. Although switching to hook is a bit easier said than done as it requires you to build it through LinuxKit |
Had the same issue using osie-v0-n=404,c=c35a5f8,b=master, have you tried newer builds of osie? According to the action hub page for kexec this happens because the kernel that "tinkie"(I'm guessing it means osie) is running doesn't support kexec. |
I'm having the same issue with |
@jimmyat did you get a chance to test with Hook to confirm that it fixed kexec for you? |
Closing due to inactivity and under the assumption that hook does not have this issue. |
When using the example listed at https://docs.tinkerbell.org/deploying-operating-systems/examples-debian/ I can't seem to get kexec working- I get a "function not implemented" error. It's unclear if this is due to a lack of kexec support in OSIE (should I be using OSIE?) or somewhere else.
Expected Behaviour
Using the example at the link above should execute kexec to switch to the new debian kernel after streaming the image.
Current Behaviour
The kexec action goes to
STATE_FAILED
with the error:function not implemented
.Possible Solution
Unsure if this down to OSIE or the debian image; suspect the former since afaik Debian Buster has exec support baked-in by default. Should I be using OSIE, or do the examples require something different (hook?)
Steps to Reproduce (for bugs)
Create the template using the first example in https://docs.tinkerbell.org/deploying-operating-systems/examples-debian/
Create a workflow and boot the VM, observe the results.
Context
I am unable to use the kexec action and the workflow does not complete.
possibly related to #80
Your Environment
MacOS, using the vagrant method.
The text was updated successfully, but these errors were encountered: