I did a "pip install -U jinja2", then "pip install jinja2", and it appears 
to have installed 2.11.1.  Now the playbook runs, so that must've been it.  

Now I need to figure out how to check the other 2 gluster volumes at the 
same time, then do each gluster server 1 at a time.  But that's another 
topic that I won't go into here.  Yet.

Thanks,
Harry

On Tuesday, March 3, 2020 at 9:14:34 AM UTC-5, harry devine wrote:
>
> My system is RHEL 7.7.  The version of jinja2 is 2.7.2 and there isn't a 
> newer version available:
>
>  [root@server1 ~]#rpm -qa python-jinja2
> python-jinja2-2.7.2-4.el7.noarch
>
> Harry
>
> On Tuesday, March 3, 2020 at 8:38:23 AM UTC-5, Felix Fontein wrote:
>>
>> Hi, 
>>
>> > Well, I'm obviously completely misunderstanding something.  Here's 
>> > what the playbook looks like: 
>> > [...] 
>> > fatal: [server1]: FAILED! => {"msg": "The conditional check 
>> > 'home_heal_status.glusterfs.heal_info | 
>> > selectattr('no_of_entries','ne','0') | list | count == 0' failed. The 
>> > error was: no test named 'ne'"} 
>> > 
>> > Sure looks like 'ne' doesn't exist to me! 
>>
>> you might have an older Jinja2 version installed. IIRC the 'ne' test 
>> was not present in every version. 
>>
>> Cheers, 
>> Felix 
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/7c637bfb-b3cb-4586-8b03-9bfa6085e59d%40googlegroups.com.

Reply via email to