Public bug reported: When starting neutron-server via systemd, "systemctl start openstack-neutron" returns before the server is actually ready. So using the server directly afterwards (eg via "neutron net-list") you get a:
Unable to establish connection to http://192.168.122.96:9696/v2.0/networks.json This could be avoided if systemd's SD_NOTIFY interface would be used when starting the server and then also use that in the .service file. oslo.service already has support for SD_NOTIFY and nova is using it for some of its services. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1649234 Title: neutron-server not available after a neutron-server start via systemd Status in neutron: New Bug description: When starting neutron-server via systemd, "systemctl start openstack-neutron" returns before the server is actually ready. So using the server directly afterwards (eg via "neutron net-list") you get a: Unable to establish connection to http://192.168.122.96:9696/v2.0/networks.json This could be avoided if systemd's SD_NOTIFY interface would be used when starting the server and then also use that in the .service file. oslo.service already has support for SD_NOTIFY and nova is using it for some of its services. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1649234/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
