Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1462520

Summary:	Error validating provider after upgrading engine
Product:	[oVirt] ovirt-provider-ovn	Reporter:	Mor <mkalfon>
Component:	provider	Assignee:	Marcin Mirecki <mmirecki>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Mor <mkalfon>
Severity:	high	Docs Contact:
Priority:	medium
Version:	1.0.4	CC:	bugs, danken, mkalfon, ylavi
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-27 08:56:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mor 2017-06-18 12:14:23 UTC

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.

Comment 2 Dan Kenigsberg 2017-11-22 08:52:39 UTC

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?

Comment 3 Mor 2017-11-22 15:23:30 UTC

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?

Comment 4 Mor 2017-11-22 15:27:22 UTC

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.

Comment 5 Marcin Mirecki 2017-11-24 15:19:28 UTC

I tried this with the current master, and it works fine.
Can you please re-check.
If it fails please provider the engine log.