freebsd bad droplet.conf symlink after 10.3 upgrade
After upgrading to 10.3 (freebsd-update style), my /etc/rc.digitalocean/droplet.conf is symlinked to “.conf” instead of “<droplet>.conf”. the quick fix was to copy my “<droplet>.conf” to “.conf” and reboot.
Why isn’t /etc/rc.d/digitalocean grabbing my droplet id from http://169.254.169.254/metadata/v1/id and creating the symlink? it times out such that DROPLET_ID is an empty string and thus the “.conf” symlink.
i compared my /etc/ files with a brand new 10.3 droplet and i didn’t see any noticeable differences.
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.×