Bug 1311047 - Ovirt Node installation fails if Enable Gluster Service option is checked
Summary: Ovirt Node installation fails if Enable Gluster Service option is checked
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Host-Deploy
Version: 3.6.2.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Itamar Heim
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-23 09:19 UTC by erick
Modified: 2016-03-23 10:28 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-03-23 10:28:25 UTC
oVirt Team: Node
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
engine host deploy log (409.02 KB, text/plain)
2016-02-23 09:19 UTC, erick
no flags Details

Description erick 2016-02-23 09:19:16 UTC
Created attachment 1129681 [details]
engine host deploy log

Description of problem:

Adding a fresh node installed with ovirt-node-iso-3.6-0.999.201602201021.el7.centos shows installation failed.

Action Items:
Gluster command failed on server.

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

ovirt-node-iso-3.6-0.999.201602201021.el7.centos
oVirt Engine Version: 3.6.2.6-1.el7.centos

How reproducible:

happens on 2 completely different servers with exact same result


Steps to Reproduce:
1. Add cluster 3.6 with the following options checked:
Enable Virt Service 
Enable Gluster Service 
2. add host freshly installed with ovirt-node-iso-3.6-0.999.201602201021.el7.centos
3. wait for installation to end

Actual results:
install failed

Expected results:
install success

Additional info:

If option is not selected, installation is successful

Comment 1 erick 2016-02-23 20:25:31 UTC
sorry i mean If option "Enable Gluster Service " is not selected, installation is successful

Comment 2 Fabian Deutsch 2016-03-23 10:28:25 UTC
Gluster is not supported in the current Node.

But oVirt Node Next is much closer to vdsm+CentOS hosts and this should be working there.


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