Created attachment 1670787 [details] Engine test is fine but adding provider failes Description of problem: After connection to cnv provider was succesfully tested, clicking on OK will result in internal engine error check picture Version-Release number of selected component (if applicable): 4.4.00-26 How reproducible: 100% Steps to Reproduce: 1. add provider to engine 2. test correctness of information in fields by test button 3. Click OK to actually add provider to the engine Actual results: Internal engine error Expected results: Add provider to engine properly Additional info: access to env was provided to dev
Please add (or paste) the content of the exception thrown in engine.log (or maybe even in server.log) when the action fails.
The issue with the provider is that it fails to parse existing vm definition: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at l ine 1 column 977 path $.items[0].spec.dataVolumeTemplates[0].spec.pvc.accessModes[0] There is a discrepancy between api definition in kubevirt and kubernetes. This issue needs to be fixed in kubevirt first and we need to regenerate java client later. @Stu should we open kubevirt specific BZ or github issue?
This BZ is dependent on https://github.com/kubevirt/kubevirt/issues/3177 once it is fixed we need to regenerate the client.
Proposed patch workarounds the issue so we do not need to wait on Kubevirt to resolve issue #3177.
Software Version:4.4.1.5-0.17.el8ev provider added normally
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3247