Bug 1462520 - Error validating provider after upgrading engine
Summary: Error validating provider after upgrading engine
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ovirt-provider-ovn
Classification: oVirt
Component: provider
Version: 1.0.4
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ovirt-4.2.0
: ---
Assignee: Marcin Mirecki
QA Contact: Mor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-18 12:14 UTC by Mor
Modified: 2017-12-04 14:06 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-11-27 08:56:42 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.