Description of problem: improper exception handling — printing to std. org.ovirt.engine.api.restapi.types.MappingLocator.MethodInvokerMapper#map
tested via artifically throwing exception in method org.ovirt.engine.api.restapi.types.MappingLocator.MethodInvokerMapper#map simulating failure of invoking Mapper via reflect api. In that case, MappingExceptionMapper is correctly invoked, producing expected output: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <fault> <reason>Operation Failed</reason> </fault> Problem is (somehow, without stacktrace) logged into engine.log However, when different exception is thrown here, this exception is printed to the output with full stacktrace, which could be considered as coding error (user should not be interrested in stacktraces in any way) and security issue(nobody but us should be informed about details of failure), both indicate exception handling error on some toplevel class. Will be discussed and potentially addressed in separate bug. But change related to this bug works as expected.
rhev 3.5.0 was released. closing.