Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1299961

Summary: Host stays in installing state when cluster compatibility version is set to 3.5
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: GeneralAssignee: Moti Asayag <masayag>
Status: CLOSED DUPLICATE QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.2CC: bugs, masayag, oourfali, pmatyas, pstehlik
Target Milestone: ---Flags: pmatyas: planning_ack?
pmatyas: devel_ack?
pmatyas: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-20 08:34:25 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:
Embargoed:
Attachments:
Description Flags
logs and screenshot none

Description Petr Matyáš 2016-01-19 15:45:29 UTC 
Description of problem:
After successful installation of host in RHEVM 3.6 with 3.5 cluster compatibility version, host stays in Installing state and I'm unable to do anything with it.

Workaround is to change the state in database (vds_dynamic table)

Version-Release number of selected component (if applicable):
3.6.2-9

How reproducible:
always

Steps to Reproduce:
1. have 3.6 engine
2. create cluster with 3.5 compatibility version
3. add and install host in that cluster

Actual results:
host in installing state

Expected results:
host up

Additional info:
Comment 1 Oved Ourfali 2016-01-20 06:40:10 UTC 
Petr - logs?
Moti, perhaps this is a duplicate of Bug 1299232?
Comment 2 Moti Asayag 2016-01-20 07:10:26 UTC 
(In reply to Oved Ourfali from comment #1)
> Petr - logs?
> Moti, perhaps this is a duplicate of Bug 1299232?

Probably. We can verify it for sure when the sengine.log and the erver.log are attached, but the symptoms are exactly the same.
Comment 3 Petr Matyáš 2016-01-20 08:15:29 UTC 
Created attachment 1116548 [details]
logs and screenshot

Weird, bugzilla had some problem with tar.gz
Comment 4 Moti Asayag 2016-01-20 08:34:25 UTC 
The log confirms this is the same issue. Closing as duplicate of Bug 1299232

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