OpenStack Compute (nova)

  1. Bug #1079387
  2. Comment #4

Comment 4 for bug 1079387

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/folsom)

Reviewed: https://review.openstack.org/16303
Committed: http://github.com/openstack/nova/commit/55d1412dc0adeae0ced23aa330213db2ce6d7f61
Submitter: Jenkins
Branch: stable/folsom

commit 55d1412dc0adeae0ced23aa330213db2ce6d7f61
Author: Sean Dague <email address hidden>
Date: Thu Nov 15 19:00:33 2012 -0500

    don't explode if a 413 didn't set Retry-After

    We use 413 error code not only for temporary out of memory
    conditions but also for over quota issues. These kinds of
    requests don't set a Retry-After header, but the code assumed
    that was a valid key, thus exploding on a KeyError. Issue
    caught in looking at tempest traces.

    Fixes bug #1079387

    Change-Id: Id406ab0799a35220b189b2e5292be092eb821ec5