Comment 1 for bug 1501046

So this behavior happens when glanceclient already received image information. You can at least get an info trhough API as workaround.
The root cause is in schema validation after receiving this info. Need to think more about this case.