Comment 4 for bug 1586023

This problem is seen in R3.1 also.
Earlier it was observed that the neutron server was running at the end of provisioning and failed while running the sanity (couldn't root cause the problem).
But this time on R3.1 build2, neutron server is down after provision is completed.
Job didn't run sanity, it was stopped after provision completed.

Again there is not much info from the log, setup is in the failed state (nodei31)

[root@nodei31 ~]# service neutron-server status
Redirecting to /bin/systemctl status neutron-server.service
● neutron-server.service - OpenStack Neutron Server
   Loaded: loaded (/usr/lib/systemd/system/neutron-server.service; enabled; vendor preset: disabled)
   Active: failed (Result: timeout) since Mon 2016-07-18 13:05:32 IST; 9min ago
 Main PID: 1552 (code=killed, signal=TERM)

Jul 18 13:02:23 nodei31.englab.juniper.net systemd[1]: Starting OpenStack Neutron Server...
Jul 18 13:05:32 nodei31.englab.juniper.net systemd[1]: neutron-server.service start operation timed out. Terminating.
Jul 18 13:05:32 nodei31.englab.juniper.net systemd[1]: Failed to start OpenStack Neutron Server.
Jul 18 13:05:32 nodei31.englab.juniper.net systemd[1]: Unit neutron-server.service entered failed state.
Jul 18 13:05:32 nodei31.englab.juniper.net systemd[1]: neutron-server.service failed.
[root@nodei31 ~]#