Any update here?
(In reply to Assaf Muller from comment #1) > Any update here? WRT systemd, this was fixed upstream - https://github.com/rdo-packages/neutron-distgit/blob/rpm-master/neutron-server.service#L13 I'll check with Brent whether we configure max_retries to -1 with tripleo
(In reply to Jakub Libosvar from comment #2) > (In reply to Assaf Muller from comment #1) > > Any update here? > > WRT systemd, this was fixed upstream - > https://github.com/rdo-packages/neutron-distgit/blob/rpm-master/neutron- > server.service#L13 > > I'll check with Brent whether we configure max_retries to -1 with tripleo I checked on OSP10 deployment and we do have everything set for overcloud controller services. We lack this behavior in undercloud though.
Brent please see comment 3. Lacking max_retries on undercloud Neutron.
It is correct to have it set on the overcloud only (at least until we have undercloud HA). The reason we have it on the overcloud HA is because we cannot guarantee that the backend services (db, rabbit, etc) are up before the systemd-managed services (like neutron). So I think this should be ON_QA at this point?
(In reply to Michele Baldessari from comment #5) > It is correct to have it set on the overcloud only (at least until we have > undercloud HA). The reason we have it on the overcloud HA is because we > cannot guarantee that the backend services (db, rabbit, etc) are up before > the systemd-managed services (like neutron). So I think this should be ON_QA > at this point? Roger that.
The code verified on python-neutron-9.0.0-0.20160929051647.71f2d2b.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-2948.html