Comment 5 for bug 1398838

So, IMO, we needn't any change on glance side to fix this defect, with the change #148387 we can just extract a well formatted human readable error message from response content, instead of printing json directly any more (that is what result this report asked I consider). Btw, the glanceclient change already covered the formation logic for text/html content of exception response.

I think we might have a few cases which may return pre-defined webob exception html content, as you mentioned case (currently I didn't try to check these cases out, and I think we can fix them be defect-driven/case-by-case), the solution in my now mind is 1). to complete missed context message/info for exception object; 2) to prepare a json serializer to organize content of webob exception/fault response based on these context message/info. However, I think we can use a dedicated change to cover this stuff.