Comment 7 for bug 1798688

Looking at the logs:

http://logs.openstack.org/26/615126/5/check/tempest-full/69d913a/controller/logs/screen-n-sch.txt.gz#_Nov_06_19_48_36_930958

We'd see these messages if we were retrying:

                LOG.debug(
                    'Unable to %(op)s because %(reason)s; retrying...',
                    {'op': e.operation, 'reason': e.reason})
        LOG.error('Failed scheduler client operation %s: out of retries',
                  f.__name__)

But I don't see those, so likely something changed in the placement error response message which makes our retry code no longer work.