Bug 1496499 - java.lang.IllegalArgumentException: VdsFenceOptionMapping has no value for version: general
Summary: java.lang.IllegalArgumentException: VdsFenceOptionMapping has no value for ve...
Keywords:
Status: CLOSED DUPLICATE of bug 1494955
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Miroslava Voglova
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-27 15:20 UTC by Petr Matyáš
Modified: 2017-09-29 14:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-29 14:28:23 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: blocker+


Attachments (Terms of Use)
engine log (369.76 KB, text/plain)
2017-09-27 15:20 UTC, Petr Matyáš
no flags Details

Description Petr Matyáš 2017-09-27 15:20:41 UTC
Created attachment 1331471 [details]
engine log

Description of problem:
When executing fence status from host edit dialogue I get this exception in engine log java.lang.IllegalArgumentException: VdsFenceOptionMapping has no value for version: general

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20170926175518.git0d20200.el7.centos.noarch

How reproducible:
always

Steps to Reproduce:
1. add fence agent
2. click on test
3.

Actual results:
traceback in engine log

Expected results:
no traceback and working test of fence agent, however I get the power status in the edit fence agent dialogue

Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2017-09-27 18:07:50 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Miroslava Voglova 2017-09-29 14:28:23 UTC

*** This bug has been marked as a duplicate of bug 1494955 ***


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