But I think it is wider than this. It seems to me there's a problem with how exception are handled in Quantum server and python-quantum-client.
The assumption in the commentary " # If QuantumError key is found, it will definitely contain a 'message' and 'type' keys?" does not hold anymore, I think. If you look how quantum server Exception are built (quantum/api/v2/resource.py::resource() body = serializer.serialize({'QuantumError': e}). e could be one of the exception defined in (quantum/common/exception.py). There's not mention to 'detail' or 'type' anymore.
In other word, I can't figure out how could the flag bad_quantum_error_flag stay set to "false".
Yep I confirm this.
But I think it is wider than this. It seems to me there's a problem with how exception are handled in Quantum server and python- quantum- client.
The assumption in the commentary " # If QuantumError key is found, it will definitely contain a 'message' and 'type' keys?" does not hold anymore, I think. If you look how quantum server Exception are built (quantum/ api/v2/ resource. py::resource( ) body = serializer. serialize( {'QuantumError' : e}). e could be one of the exception defined in (quantum/ common/ exception. py). There's not mention to 'detail' or 'type' anymore.
In other word, I can't figure out how could the flag bad_quantum_ error_flag stay set to "false".