First Last Prev Next    This bug is not in your last search results.
Bug 1462520 - Error validating provider after upgrading engine
Error validating provider after upgrading engine
Status: NEW
Product: ovirt-provider-ovn
Classification: oVirt
Component: provider (Show other bugs)
1.0.4
Unspecified Unspecified
medium Severity high
: ovirt-4.2.0
: ---
Assigned To: Marcin Mirecki
Mor
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2017-06-18 08:14 EDT by Mor
Modified: 2017-09-28 04:33 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.2+

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Mor 2017-06-18 08:14:23 EDT 
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.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.