Bug 1311047 - Ovirt Node installation fails if Enable Gluster Service option is checked
Ovirt Node installation fails if Enable Gluster Service option is checked
Product: ovirt-engine
Classification: oVirt
Component: Host-Deploy (Show other bugs)
x86_64 Linux
unspecified Severity high (vote)
: ---
: ---
Assigned To: Itamar Heim
Pavel Stehlik
Depends On:
  Show dependency treegraph
Reported: 2016-02-23 04:19 EST by erick
Modified: 2016-03-23 06:28 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-03-23 06:28:25 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Node
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
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 04:19 EST, erick
no flags Details

  None (edit)
Description erick 2016-02-23 04:19:16 EST
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 Engine Version:

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 15:25:31 EST
sorry i mean If option "Enable Gluster Service " is not selected, installation is successful
Comment 2 Fabian Deutsch 2016-03-23 06:28:25 EDT
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.