Bug 1332100 - Re-install host failed with General command validation failure
Summary: Re-install host failed with General command validation failure
Keywords:
Status: CLOSED DUPLICATE of bug 1329979
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.0.0
Hardware: x86_64
OS: Linux
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Oved Ourfali
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-02 08:38 UTC by Michael Burman
Modified: 2016-05-03 07:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-03 07:20:52 UTC
oVirt Team: Infra
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?


Attachments (Terms of Use)
attempt1 (261.32 KB, application/x-gzip)
2016-05-02 08:38 UTC, Michael Burman
no flags Details
attempt2 (311.86 KB, application/x-gzip)
2016-05-02 08:39 UTC, Michael Burman
no flags Details

Description Michael Burman 2016-05-02 08:38:17 UTC
Created attachment 1152881 [details]
attempt1

Description of problem:
Re-install host failed with General command validation failure. 

It's not possible to re-install a host in cluster 4.0 after failing in the first time, because of a compatibility issues. 
 
Version-Release number of selected component (if applicable):
4.0.0-0.0.master.20160423161403.gite38df80.el7.centos

How reproducible:
100

Steps to Reproduce:
1. Try to install host(vdsm 3.6.z) in cluster 4.0 and fail with:
"Host orchid-vds2.qa.lab.tlv.redhat.com is compatible with versions (3.4,3.5,3.6) and cannot join Cluster CL1 which is set to version 4.0"
2. Put host to maintenance and update vdsm to 4.0 on host
3. Try to re-install the host

Actual results:
Re-install host failed with General command validation failure -->

Error while executing action: 

orchid-vds2.qa.lab.tlv.redhat.com:
General command validation failure.

Expected results:
Re-install should work

Additional info:
Removing the server and then installing it works

Comment 1 Michael Burman 2016-05-02 08:39:03 UTC
Created attachment 1152882 [details]
attempt2

Comment 2 Martin Perina 2016-05-03 07:20:52 UTC
NPE exception stacktrace is the same as in BZ1329979, the issue was caused most probably by errors in changes done in multiple action runners.

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


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