<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 19/08/2016 à 13:43, Sahina Bose a
écrit :<br>
</div>
<blockquote
cite="mid:CACjzOvf4_vEzdG=ZdzsD4Neddu8JdOWnL5YX-4jHLGVsgS2usA@mail.gmail.com"
type="cite">
<div dir="ltr"><span class=""></span><br>
<span class=""> </span>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> Or are you adding the 3 nodes to your
existing cluster? If so, I suggest you try
adding this to a new cluster<br>
</div>
</div>
</div>
</div>
</blockquote>
</span> OK, I tried and succeed to create a new cluster.<br>
In this new cluster, I was ABLE to add the first new
host, using its mgmt DNS name.<br>
This first host still has to have its NICs configured,
and (using Chrome or FF) the access to the network
settings window is stalling the browser (I tried to
restart even the engine, to no avail). Thus, I can not
setup this first node NICs.<br>
<br>
Thus, I can not add any further host because oVirt
relies on a first host to validate the further ones.<span
class=""><font color="#888888"><br>
</font></span></div>
</blockquote>
<div><br>
<br>
</div>
<div>Network team should be able to help you here.<br>
</div>
</div>
<br>
</div>
</div>
</blockquote>
<br>
OK, there were no mean I could continue this way (browser crash), so
I tried and succeed doing so :<br>
- remove the newly created host and cluster<br>
- create a new DATACENTER<br>
- create a new cluster in this DC<br>
- add the first new host : OK<br>
- add the 2 other new hosts : OK<br>
<br>
Now, I can smoothly configure their NICs.<br>
<br>
Doing all this, I saw that oVirt detected there already was existing
gluster cluster and volume, and integrated it in oVirt.<br>
<br>
Then, I was able to create a new storage domain in this new DC and
cluster, using one of the *gluster* FQDN's host. It went nicely.<br>
<br>
BUT, when viewing the volume tab and brick details, the displayed
brick names are the host DNS name, and NOT the host GLUSTER DNS
names.<br>
<br>
I'm worrying about this, confirmed by what I read in the logs :<br>
<br>
2016-08-19 14:46:30,484 WARN
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturnForXmlRpc]
(DefaultQuartzScheduler_Worker-100) [107dc2e3] Could not associate
brick 'serv-vm-al04-data.sdis.isere.fr:/gluster/data/brick04<br>
' of volume '35026521-e76e-4774-8ddf-0a701b9eb40c' with correct
network as no gluster network found in cluster
'1c8e75a0-af3f-4e97-a8fb-2f7ef3ed9f30'<br>
2016-08-19 14:46:30,492 WARN
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturnForXmlRpc]
(DefaultQuartzScheduler_Worker-100) [107dc2e3] Could not associate
brick 'serv-vm-al05-data.sdis.isere.fr:/gluster/data/brick04<br>
' of volume '35026521-e76e-4774-8ddf-0a701b9eb40c' with correct
network as no gluster network found in cluster
'1c8e75a0-af3f-4e97-a8fb-2f7ef3ed9f30'<br>
2016-08-19 14:46:30,500 WARN
[org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturnForXmlRpc]
(DefaultQuartzScheduler_Worker-100) [107dc2e3] Could not associate
brick 'serv-vm-al06-data.sdis.isere.fr:/gluster/data/brick04<br>
' of volume '35026521-e76e-4774-8ddf-0a701b9eb40c' with correct
network as no gluster network found in cluster
'1c8e75a0-af3f-4e97-a8fb-2f7ef3ed9f30'<br>
<br>
[oVirt shell (connected)]# list clusters<br>
<br>
id : 00000001-0001-0001-0001-000000000045<br>
name : cluster51<br>
description: Cluster d'alerte de test<br>
<br>
id : 1c8e75a0-af3f-4e97-a8fb-2f7ef3ed9f30<br>
name : cluster52<br>
description: Cluster d'alerte de test<br>
<br>
[oVirt shell (connected)]# <br>
<br>
"cluster52" is the recent cluster, and I do have a dedicated gluster
network, marked as gluster network, in the correct DC and cluster.<br>
The only point is that :<br>
- Each host has its name ("serv-vm-al04") and a second name for
gluster ("serv-vm-al04-data").<br>
- Using blahblahblah-data is correct on a gluster point of view<br>
- Maybe oVirt is disturb not to be able to ping the gluster FQDN
(not routed) and then throwing this error?<br>
<br>
-- <br>
Nicolas ECARNOT<br>
</body>
</html>