Encountering Error when trying to change my kernel through control panel

Posted May 15, 2019 1.8k views

When I try to update my droplet’s kernel to use Grub I get the following error message:

Error processing change_kernel action.

Any clues?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
10 answers

Hey there,

Thanks for letting us know about this. We’ve been made aware of a recent issue on our side where particular Droplets with internally managed kernels show the kernel selection menu, despite the fact that the kernel is managed on the Droplet itself.

For these Droplets, you can safely ignore the kernel selector tool for now since it doesn’t function. Once the issue is resolved on our side, you’ll see the proper messaging instead:

“The kernel for this Droplet is not managed within the control panel. Instead, you can upgrade the kernel from within the Droplet. Learn more.”

For now, feel free to reach out to our support team so that we can confirm whether your Droplet is indeed affected by this issue! We appreciate your understanding here.

I am having the same problem. Trying to mitigate the MDS vulnerability, and I can’t change this setting as recommended.

same here, can’t change it.

I have the same problem. It happens when I try to change to Grub or any other type.

Same thing here. Let us know if you find a solution.

Same. Hoping by adding enough comments here, it will send it up the support ladder a little faster.

Got the same issue here.. added a support-ticket for it! If everyone adds everyones ticket-number in their ticket, they might bulk it? :D Might go faster?

Mine is:
[Ticket #2679510] Error processing change_kernel action.

I see a Select a Kernel *menu with a *Change button and I see the verbiage “This will update your configuration. Then power off the server from the command line and boot it from the control panel and the new kernel will be active. To revert, simply select ‘Original Kernel’ and follow the same process.” but I have updated my kernel on the command line, powered down, and restarted, and I also see in the control panel that my Droplet’s current kernel is DigitalOcean GrubLoader v0.2 (20160714) CentOS. I think these are mixed messages. Is this the bug others are describing here?