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 <[email protected]> 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 -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected]/message/LLTMHW7JIGLIE6JPSL7DPER6YBHNYD33/ >
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/CXKU47UZCVN4JR7IFCYAMHU7DZ3KH2NO/
