4.5.2 Create Additional Gluster Logical Volumes fails
Hi, In 4.4 adding additional gluster volumes was a simple ansible task (or via cockpit). With 4.5.2 I tried to add new volumes but the logic has changed/broken. Here's the error I am getting: TASK [gluster.infra/roles/backend_setup : Create volume groups] ******************************************************************************************************************************** failed: [bdtovirthcidmz02-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.010442", "end": "2022-11-10 13:11:16.717772", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:11:16.707330", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} failed: [bdtovirthcidmz03-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.010231", "end": "2022-11-10 13:12:35.607565", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:12:35.597334", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} failed: [bdtovirthcidmz01-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.011282", "end": "2022-11-10 13:13:24.336233", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:13:24.324951", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} The vg was created as part of the initial ansible build with logical volumes being added when required. Any assistance would be greatly appreciated. Kind regards Simon
Is this because lvmdevices has removed the requirement for lvm filter? Obviously the change to lvmdevices occurred post initial gluster volume creation - but how do we I fix it? "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 16:02:45.225250", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [ " Configuration setting \"filter\" invalid. It's not part of any section.",
Does anyone have any input please?
Am I really the only user to try and create new gluster volumes on an existing vg? Has anyone succeeded in doing this on 4.5.2?
I have upgraded all 3 nodes to the latest 4.5.3 and still unable to add additional gluster volumes to the same thinpool/vg There was never an issue prior to 4.5 TASK [gluster.infra/roles/backend_setup : Create volume groups] ******************************************************************************************************************************** failed: [bdtovirthcidmz02-strg.maskeddomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.010474", "end": "2022-11-21 16:46:59.090880", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-21 16:46:59.080406", "stderr": " /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} failed: [bdtovirthcidmz03-strg.maskeddomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.010713", "end": "2022-11-21 16:48:21.283404", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-21 16:48:21.272691", "stderr": " /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} failed: [bdtovirthcidmz01-strg.maskeddomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.011136", "end": "2022-11-21 16:49:09.188463", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-21 16:49:09.177327", "stderr": " /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []}
Any ideas please @Strahil @Sandro @Yedidyah
Bump
Bump
@Gobinda Das <godas@redhat.com> maybe you can connect Simon to someone who can help? Il giorno gio 10 nov 2022 alle ore 12:40 <simon@justconnect.ie> ha scritto:
Hi,
In 4.4 adding additional gluster volumes was a simple ansible task (or via cockpit).
With 4.5.2 I tried to add new volumes but the logic has changed/broken. Here's the error I am getting:
TASK [gluster.infra/roles/backend_setup : Create volume groups] ******************************************************************************************************************************** failed: [bdtovirthcidmz02-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.010442", "end": "2022-11-10 13:11:16.717772", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:11:16.707330", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} failed: [bdtovirthcidmz03-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.010231", "end": "2022-11-10 13:12:35.607565", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:12:35.597334", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} failed: [bdtovirthcidmz01-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.011282", "end": "2022-11-10 13:13:24.336233", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:13:24.324951", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []}
The vg was created as part of the initial ansible build with logical volumes being added when required.
Any assistance would be greatly appreciated.
Kind regards
Simon _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SQVROUOCSLKYAF...
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle OS Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*
Can you please provide me the output of below command? rpm -qa | grep gluster-ansible On Thu, Nov 24, 2022 at 2:43 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
@Gobinda Das <godas@redhat.com> maybe you can connect Simon to someone who can help?
Il giorno gio 10 nov 2022 alle ore 12:40 <simon@justconnect.ie> ha scritto:
Hi,
In 4.4 adding additional gluster volumes was a simple ansible task (or via cockpit).
With 4.5.2 I tried to add new volumes but the logic has changed/broken. Here's the error I am getting:
TASK [gluster.infra/roles/backend_setup : Create volume groups] ******************************************************************************************************************************** failed: [bdtovirthcidmz02-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.010442", "end": "2022-11-10 13:11:16.717772", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:11:16.707330", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} failed: [bdtovirthcidmz03-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.010231", "end": "2022-11-10 13:12:35.607565", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:12:35.597334", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []} failed: [bdtovirthcidmz01-strg.mydomain.com] (item={'key': 'gluster_vg_sda', 'value': [{'vgname': 'gluster_vg_sda', 'pvname': '/dev/sda'}]}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["vgcreate", "--dataalignment", "2048K", "-s", "2048K", "gluster_vg_sda", "/dev/sda"], "delta": "0:00:00.011282", "end": "2022-11-10 13:13:24.336233", "item": {"key": "gluster_vg_sda", "value": [{"pvname": "/dev/sda", "vgname": "gluster_vg_sda"}]}, "msg": "non-zero return code", "rc": 3, "start": "2022-11-10 13:13:24.324951", "stderr": " Configuration setting \"filter\" invalid. It's not part of any section.\n /dev/gluster_vg_sda: already exists in filesystem\n Run `vgcreate --help' for more information.", "stderr_lines": [" Configuration setting \"filter\" invalid. It's not part of any section.", " /dev/gluster_vg_sda: already exists in filesystem", " Run `vgcreate --help' for more information."], "stdout": "", "stdout_lines": []}
The vg was created as part of the initial ansible build with logical volumes being added when required.
Any assistance would be greatly appreciated.
Kind regards
Simon _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SQVROUOCSLKYAF...
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle OS
Red Hat EMEA <https://www.redhat.com/>
sbonazzo@redhat.com <https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*
-- Thanks, Gobinda
Thanks Sandro/Gobinda, [root@pgsovirthcidmz01 ~]# rpm -qa | grep gluster-ansible gluster-ansible-roles-1.0.5-28.el8.noarch gluster-ansible-infra-1.0.4-22.el8.noarch gluster-ansible-maintenance-1.0.1-12.el8.noarch gluster-ansible-cluster-1.0-5.el8.noarch gluster-ansible-repositories-1.0.1-5.el8.noarch gluster-ansible-features-1.0.5-15.el8.noarch [root@pgsovirthcidmz01 ~]# Kind Regards Simon
Gobinda, Looks like this issue arises because of changes in ansibles roles made to support ansible-core. I think the gluster ansible module was used to handle this and when we moved to CLI this is been not taken care of. On Thu, Nov 24, 2022 at 5:06 PM <simon@justconnect.ie> wrote:
Thanks Sandro/Gobinda,
[root@pgsovirthcidmz01 ~]# rpm -qa | grep gluster-ansible gluster-ansible-roles-1.0.5-28.el8.noarch gluster-ansible-infra-1.0.4-22.el8.noarch gluster-ansible-maintenance-1.0.1-12.el8.noarch gluster-ansible-cluster-1.0-5.el8.noarch gluster-ansible-repositories-1.0.1-5.el8.noarch gluster-ansible-features-1.0.5-15.el8.noarch [root@pgsovirthcidmz01 ~]#
Kind Regards
Simon _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LLTMHW7JIGLIE6...
Is there any intention to fix this issue? On 25 Nov 2022, at 11:06, Ritesh Chikatwar <rchikatw@redhat.com> wrote: Gobinda, Looks like this issue arises because of changes in ansibles roles made to support ansible-core. I think the gluster ansible module was used to handle this and when we moved to CLI this is been not taken care of. On Thu, Nov 24, 2022 at 5:06 PM <simon@justconnect.ie<mailto:simon@justconnect.ie>> wrote: Thanks Sandro/Gobinda, [root@pgsovirthcidmz01 ~]# rpm -qa | grep gluster-ansible gluster-ansible-roles-1.0.5-28.el8.noarch gluster-ansible-infra-1.0.4-22.el8.noarch gluster-ansible-maintenance-1.0.1-12.el8.noarch gluster-ansible-cluster-1.0-5.el8.noarch gluster-ansible-repositories-1.0.1-5.el8.noarch gluster-ansible-features-1.0.5-15.el8.noarch [root@pgsovirthcidmz01 ~]# Kind Regards Simon _______________________________________________ Users mailing list -- users@ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LLTMHW7JIGLIE6...
On Fri, Nov 25, 2022 at 4:37 PM Ritesh Chikatwar <rchikatw@redhat.com> wrote:
Gobinda, Looks like this issue arises because of changes in ansibles roles made to support ansible-core. I think the gluster ansible module was used to handle this and when we moved to CLI this is been not taken care of.
Thanks Ritesh for ponting the root cause. If you have some time, can you please check how much effort is needed to fix this or if it's a simple fix can we have an upstream patch?
On Thu, Nov 24, 2022 at 5:06 PM <simon@justconnect.ie> wrote:
Thanks Sandro/Gobinda,
[root@pgsovirthcidmz01 ~]# rpm -qa | grep gluster-ansible gluster-ansible-roles-1.0.5-28.el8.noarch gluster-ansible-infra-1.0.4-22.el8.noarch gluster-ansible-maintenance-1.0.1-12.el8.noarch gluster-ansible-cluster-1.0-5.el8.noarch gluster-ansible-repositories-1.0.1-5.el8.noarch gluster-ansible-features-1.0.5-15.el8.noarch [root@pgsovirthcidmz01 ~]#
Kind Regards
Simon _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LLTMHW7JIGLIE6...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CXKU47UZCVN4JR...
-- Thanks, Gobinda
Hello, I will look into this and get back to you by next week. This week i am busy some priority work. On Mon, Nov 28, 2022 at 2:53 PM Gobinda Das <godas@redhat.com> wrote:
On Fri, Nov 25, 2022 at 4:37 PM Ritesh Chikatwar <rchikatw@redhat.com> wrote:
Gobinda, Looks like this issue arises because of changes in ansibles roles made to support ansible-core. I think the gluster ansible module was used to handle this and when we moved to CLI this is been not taken care of.
Thanks Ritesh for ponting the root cause. If you have some time, can you please check how much effort is needed to fix this or if it's a simple fix can we have an upstream patch?
On Thu, Nov 24, 2022 at 5:06 PM <simon@justconnect.ie> wrote:
Thanks Sandro/Gobinda,
[root@pgsovirthcidmz01 ~]# rpm -qa | grep gluster-ansible gluster-ansible-roles-1.0.5-28.el8.noarch gluster-ansible-infra-1.0.4-22.el8.noarch gluster-ansible-maintenance-1.0.1-12.el8.noarch gluster-ansible-cluster-1.0-5.el8.noarch gluster-ansible-repositories-1.0.1-5.el8.noarch gluster-ansible-features-1.0.5-15.el8.noarch [root@pgsovirthcidmz01 ~]#
Kind Regards
Simon _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LLTMHW7JIGLIE6...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CXKU47UZCVN4JR...
--
Thanks, Gobinda
Sorry to hassle you Ritesh but do you have an update please? Kind regards Simon...
Please let me know if this is likely to be a quick fix - if not I'll have to manually created additional volumes. Regards Simon
Hello Simon, This might take time some time (2-3 weeks) I think it's better if you can go ahead and create the volume manually. I will update here once this fix is available. On Thu, Dec 15, 2022 at 10:59 AM <simon@justconnect.ie> wrote:
Please let me know if this is likely to be a quick fix - if not I'll have to manually created additional volumes.
Regards
Simon _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/MHQXOTBXTLLAVA...
Hi Ritesh, Any update on this please? Kind regards Simon
Hi Ritesh, Any update please? Regards Simon…
Sadly the gluster's ansible code was converted to 'non-idempotent' due to ansible changes and lack of support. I would go the manual way. Best Regards,Strahil Nikolov Hi Ritesh, Any update please? Regards Simon… _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/DDPDAUEAR3VKAF...
As a workaround I commented out the sections in the following yaml files where the VG, thinpool etc already existed /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/main.yml /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vg_create.yml /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/thin_pool_create.yml and ran the task again - It worked :)
participants (6)
-
Gobinda Das -
Ritesh Chikatwar -
Sandro Bonazzola -
Simon Scott -
simon＠justconnect.ie
-
Strahil Nikolov