Public bug reported: The problem actually has to do with the way `systemd` is configured in the latest version of Ubuntu 16.04. Setting up a typical OpenVPN configuration, and rebooting causes a Instance Status check failure in AWS EC2. The reason is because the file `/lib/systemd/system/openvpn@.service` is missing the following line:
After=network.target network-online.target The entire [Unit] section then looks like: [Unit] Description=OpenVPN connection to %i PartOf=openvpn.service ReloadPropagatedFrom=openvpn.service Before=systemd-user-sessions.service After=network.target network-online.target Documentation=man:openvpn(8) Documentation=https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage Documentation=https://community.openvpn.net/openvpn/wiki/HOWTO This ensures that routes needed for OpenVPN configurations get called after the main networking stack. See issues here: - https://forums.aws.amazon.com/thread.jspa?messageID=719570 - https://sourceforge.net/p/openvpn/mailman/message/35078170/ ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580356 Title: OpenVPN causes reboot failure on Xenial in AWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1580356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
