Comment 2 for bug 1505325

Now with xenial, systemd stops neutron-server service after multiple attempts to start, and juju status says "blocked" appropriately. So no longer eating CPU resources infinitely.

# systemctl status neutron-server.service
● neutron-server.service - OpenStack Neutron Server
   Loaded: loaded (/lib/systemd/system/neutron-server.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Wed 2016-12-21 03:20:12 UTC; 10min ago
  Process: 23607 ExecStart=/etc/init.d/neutron-server systemd-start (code=exited, status=1/FAILURE)
  Process: 23606 ExecStartPre=/bin/chown neutron:neutron /var/lock/neutron /var/log/neutron /var/lib/neutron (code=exited, status=0/SUCCESS)
  Process: 23600 ExecStartPre=/bin/mkdir -p /var/lock/neutron /var/log/neutron /var/lib/neutron (code=exited, status=0/SUCCESS)
 Main PID: 23607 (code=exited, status=1/FAILURE)

Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: neutron-server.service: Unit entered failed state.
Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: neutron-server.service: Failed with result 'exit-code'.
Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: neutron-server.service: Service hold-off time over, scheduling restart.
Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: Stopped OpenStack Neutron Server.
Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: neutron-server.service: Start request repeated too quickly.
Dec 21 03:20:12 juju-bbb18b-0 systemd[1]: Failed to start OpenStack Neutron Server.