11:32 a.m.
Setting up oVirt with a separate cluster for storage using gluster we
discovered that the gluster services are not set to autostart for the
default runlevels.
Host(s) were clean Centos-6.5 hosts with the correct repositories and
then added from the webui. Hosts got all the packages and gluster was
correctly started for that session but after a reboot gluster isn't
running and the host was set to non-operational.
Is this a known problem and if not should I file a BZ but under which
category?
Regards,
Joop
12:38 p.m.
On 03/28/2014 04:02 PM, Joop wrote:
Setting up oVirt with a separate cluster for storage using gluster we
discovered that the gluster services are not set to autostart for the
default runlevels.
Host(s) were clean Centos-6.5 hosts with the correct repositories and
then added from the webui. Hosts got all the packages and gluster was
correctly started for that session but after a reboot gluster isn't
running and the host was set to non-operational.
Is this a known problem and if not should I file a BZ but under which
category?
Which version of gluster are you using?
[Adding gluster-users]
Regards,
Joop
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
12:57 p.m.
This is a multi-part message in MIME format.
--------------040708010002080500020208
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sorry this time to the list also.
On 03/28/2014 04:02 PM, Joop wrote:
> Setting up oVirt with a separate cluster for storage using gluster we
> discovered that the gluster services are not set to autostart for the
> default runlevels.
> Host(s) were clean Centos-6.5 hosts with the correct repositories and
> then added from the webui. Hosts got all the packages and gluster was
> correctly started for that session but after a reboot gluster isn't
> running and the host was set to non-operational.
>
> Is this a known problem and if not should I file a BZ but under which
> category?
Which version of gluster are you using?
[Adding gluster-users]
Sorry, the version that comes with the repos ovirt.repo and epel so
3.4.2. Version shouldn't matter because I expect that the hostdeploy
from ovirt-engine to take care of making sure that glusterd and
glusterfsd are started on system startup.
Joop
--------------040708010002080500020208
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 14px;" lang="x-western">Sorry this time to the list
also.<br>
<br>
<blockquote type="cite" style="color: #000000;">
<br>
On 03/28/2014 04:02 PM, Joop wrote:
<br>
<blockquote type="cite" style="color: #000000;">Setting
up oVirt
with a separate cluster for storage using gluster we
discovered that the gluster services are not set to autostart
for the default runlevels.
<br>
Host(s) were clean Centos-6.5 hosts with the correct
repositories and then added from the webui. Hosts got all the
packages and gluster was correctly started for that session
but after a reboot gluster isn't running and the host was set
to non-operational.
<br>
<br>
Is this a known problem and if not should I file a BZ but
under which category?
<br>
</blockquote>
<br>
Which version of gluster are you using?
<br>
<br>
[Adding gluster-users]
<br>
<br>
<br>
</blockquote>
Sorry, the version that comes with the repos ovirt.repo and epel
so 3.4.2. Version shouldn't matter because I expect that the
hostdeploy from ovirt-engine to take care of making sure that
glusterd and glusterfsd are started on system startup.
<br>
<br>
Joop
<br>
<br>
</div>
<br>
</body>
</html>
--------------040708010002080500020208--
4007
days inactive
4007
days old
2 comments
2 participants
participants (2)
-
Joop -
Sahina Bose