Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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.
Accepted Answer
Okay, did you confirm that you were on a previous kernel after reboot?
It’s quite difficult to know what went wrong. I would probably recommend that you start the Recovery Image (you have to request that through support) and transfer data to a new droplet. I’m guessing you don’t have backups running?
dot in 50-cloud-init.cfg makes ifup ignoring that file. after rename - all works. I am looking for resolution of work-a-round so far.
One w-a-r is a symlink on .cfg file