Red Hat Bugzilla – Bug 1462520
Error validating provider after upgrading engine
Last modified: 2017-12-04 09:06:34 EST
Description of problem: Test provider shows error "Error while executing action: A Request to the Server failed: Invalid type signature for org.ovirt.engine.core.common.action.VdcActionType" after upgrading ovirt-engine packages using engine-setup. Version-Release number of selected component (if applicable): 4.2.0-0.0.master.20170609091031.gitc86d08a.el7.centos How reproducible: 100% Steps to Reproduce: 1. Run engine-setup and upgrade available ovirt-engine packages. 2. Use test button on the default OVN provider (ovirt-provider-ovn) that was created by engine-setup. 3. Approve the certificate import. Actual results: Error is thrown - "Error while executing action: A Request to the Server failed: Invalid type signature for org.ovirt.engine.core.common.action.VdcActionType". Expected results: Should succeed.
From which Engine and provider versions have you upgraded? Is it only a problem of the Test button, or does the provider not work at all?
This bug is 5 months old and I don't keep track of version that I upgrade. Maybe we should add a logger for provider version in ovirt-provider-ovn.log, so we can easily track this?
If the provider not work at all? I'm not sure, I don't remember exactly. It was relevant for the Test button for sure.
I tried this with the current master, and it works fine. Can you please re-check. If it fails please provider the engine log.