Apologies, just saw the answer on a previous post in this same thread
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
Apologies, did not see a previous post
This works for me:
---
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
Apologies, did not see a previous post from Julie
This works for me:
---
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
Apologies, did not see a previous post from Julie
This works for me:
---
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
Apologies, did not see a previous post from Julie
This works for me:
---
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
I am having the same issue from CLI and trying to use existing gluster storage
(server1:/gluster_bricks/engine).
Error:
[ INFO ] TASK [Add glusterfs storage domain]
[ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Failed
to fetch Gluster Volume List]". HTTP response code
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
"ovirt1.localdomain:/gluster_bricks/engine”
So I am new to gluster but as a client of gluster you can only refer to it via
volume name.
host:/
Hence maybe try ovirt1.localdomain:/engine.
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
"ovirt1.localdomain:/gluster_bricks/engine”
So I am new to gluster but as a client of gluster you can only refer to it via
volume name.
host:/
Hence maybe try ovirt1.localdomain:/engine.
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
"ovirt1.localdomain:/gluster_bricks/engine”
So I am new to gluster but as a client of gluster you can only refer to it via
volume name.
host:/
Hence maybe try ovirt1.localdomain:/engine.
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
"ovirt1.localdomain:/gluster_bricks/engine”
So I am new to gluster but as a client of gluster you can only refer to it via
volume name.
host:/
Hence maybe try ovirt1.localdomain:/engine.
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
"ovirt1.localdomain:/gluster_bricks/engine”
So I am new to gluster but as a client of gluster you can only refer to it via
volume name.
host:/
Hence maybe try ovirt1.localdomain:/engine.
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
"ovirt1.localdomain:/gluster_bricks/engine”
So I am new to gluster but as a client of gluster you can only refer to it via
volume name.
host:/
Hence maybe try ovirt1.localdomain:/engine.
I had this issue this week as well.
When asked about the glusterfs that you self provisioned you stated
"ovirt1.localdomain:/gluster_bricks/engine”
So I am new to gluster but as a client of gluster you can only refer to it via
volume name.
host:/
Hence maybe try ovirt1.localdomain:/engine.
It seems that "Use existing" is not working.
I have tried multiple times to redeploy the engine and it always fails . Here
is the last log from vdsm :
2018-12-09 15:56:40,269+0200 INFO (JsonRpc (StompReactor))
[Broker.StompAdapter] Subscribe command received (stompreactor:132)
2018-12-09
It seems that I have picked the wrong deploy method. Switching to
"HyperConverged" -> "Use existing" fixes the error.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement:
15 matches
Mail list logo
