Thanks Jay, I wonder whether there is an easy-ish way to collect stats about the sorts of errors deployers see in that catchall, so that when this comes back around in a release or two there might be some less anecdotal data available...?
Cheers, On 24 May 2017 at 06:43, Jay Pipes <[email protected]> wrote: > Hello Dear Operators, > > OK, we've heard you loud and (mostly) clear. We won't remove the automated > rescheduling behavior from Nova. While we will be removing the primary cause > of reschedules (resource overconsumption races), we cannot yet eliminate the > catchall exception handling on the compute node that triggers a retry of the > instance launch. Nor will we be able to fully ameliorate the > affinity/anti-affinity last-minute violation problems for at least another > release. > > So, we'll continue to support basic retries within the originally-selected > cell. > > Best, > -jay > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Cheers, ~Blairo _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
