search for: gsaov07

On Mon, Jun 12, 2017 at 7:30 PM, Langley, Robert <Robert.Langley at ventura.org > wrote: > As far as the peer status (and I now remember seeing this earlier) the > issue appears to be that the host name for gsaov07 is attempting to resolve > over the wrong network for gluster "ent...." and not "stor.local". > So, it may be as simple as removing gsaov07 as a peer, then probing over > the correct network. > If gsaov07 doesn't have any volumes (bricks to be precise), that'...

As far as the peer status (and I now remember seeing this earlier) the issue appears to be that the host name for gsaov07 is attempting to resolve over the wrong network for gluster "ent...." and not "stor.local". So, it may be as simple as removing gsaov07 as a peer, then probing over the correct network. I'll follow up with the Engine log. Sent using OWA for iPhone __________________________...

This is in relation to bringing up a new oVirt environment. When I was bringing up oVirt (Hosted-Engine), I had the Glusterd service stopped, since the server (I have its name as GSAoV07) was initially only going to be used to host the oVirt engine as a hypervisor (it will have Gluster volumes in the near future). I have three other servers I am using for storage. One of those three is also going to be a hypervisor and the other two are dedicated storage servers (Their names are GS...

..., Langley, Robert < >> Robert.Langley at ventura.org> wrote: >> >>> This is in relation to bringing up a new oVirt environment. >>> When I was bringing up oVirt (Hosted-Engine), I had the Glusterd service >>> stopped, since the server (I have its name as GSAoV07) was initially only >>> going to be used to host the oVirt engine as a hypervisor (it will have >>> Gluster volumes in the near future). I have three other servers I am using >>> for storage. One of those three is also going to be a hypervisor and the >>> other t...

...vice up. On Fri, Jun 9, 2017 at 10:01 PM, Langley, Robert <Robert.Langley at ventura.org > wrote: > This is in relation to bringing up a new oVirt environment. > When I was bringing up oVirt (Hosted-Engine), I had the Glusterd service > stopped, since the server (I have its name as GSAoV07) was initially only > going to be used to host the oVirt engine as a hypervisor (it will have > Gluster volumes in the near future). I have three other servers I am using > for storage. One of those three is also going to be a hypervisor and the > other two are dedicated storage servers...

...17 at 10:01 PM, Langley, Robert <Robert.Langley at ventura.org<mailto:Robert.Langley at ventura.org>> wrote: This is in relation to bringing up a new oVirt environment. When I was bringing up oVirt (Hosted-Engine), I had the Glusterd service stopped, since the server (I have its name as GSAoV07) was initially only going to be used to host the oVirt engine as a hypervisor (it will have Gluster volumes in the near future). I have three other servers I am using for storage. One of those three is also going to be a hypervisor and the other two are dedicated storage servers (Their names are GS...

...9, 2017 at 10:01 PM, Langley, Robert < > Robert.Langley at ventura.org> wrote: > >> This is in relation to bringing up a new oVirt environment. >> When I was bringing up oVirt (Hosted-Engine), I had the Glusterd service >> stopped, since the server (I have its name as GSAoV07) was initially only >> going to be used to host the oVirt engine as a hypervisor (it will have >> Gluster volumes in the near future). I have three other servers I am using >> for storage. One of those three is also going to be a hypervisor and the >> other two are dedicated...