Bug 1332100

Summary: Re-install host failed with General command validation failure
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.InfraAssignee: Oved Ourfali <oourfali>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: bugs, mperina
Target Milestone: ---Flags: mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-03 07:20:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
attempt1
none
attempt2 none

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 ***