Hi guys, im currently facing the issue that if i change the rules in my configuration add some different rules and remove some the ansible playbook then applies the new created rules only and leave the old one there. is there a way to make that inheriting? if her rules are not there in the configuration anymore that the module removes them as well and not only append? cause if i make the whole filter absent it tries to delete the whole filter and this is not possible cause its used in the event notification forwarder.
#na_ontap_ems_filter module missing cleanup from old filter rules
indigo sun
bold atlas
@indigo sun Could you please share the playbook and logs? Are you using the module for the first time and facing this issue or was the module working fine before and now the behavior is changed?
https://github.com/ansible-collections/netapp.ontap/wiki/Debugging#tracing-zapi-and-rest-api-calls
indigo sun
yes we are doing a lot with ansible. this worked fine all the time but then we considered to shorten our EMS incidnet creation. So i change it from include all serverities and started to exclude what makes noice. so there we figured out that yeah if we only add it works cause it overwrite. so we asume that if we shorten the event rules list that he also overwrites everything but it only overwrite some how the indexes the module needs to use. i made a picture. so thats why i dont think that its not working properly there is just the thing that no one thought about shortening the event rule?
in the picture you see the whole ems rules we applied and then marked in red the new one we want to roll-out. but in the UAT we figured out that yeah it leave the old rule there. If we apply / roll-back to the main brach so push the old code which has more indexes it overwrites everything as it should.
if you need and want i can share of course all the LOGs you need. 🙂 just tell me where to drop it.
bold atlas
@indigo sun Can you please share the ONTAP collection version?
indigo sun
- name: netapp.ontap
version: 23.2.0
bold atlas
@indigo sun Created story DEVOPS-8124
indigo sun
@bold atlas thank you so much for digging in to it 😊
indigo sun
@bold atlas
Quick update. i created a powershell script to remove each ems rule from the syslog forwarder is send you, so that we only had the defualt rule in it.
Then the roll-out went smoothly but. there i noted that thise ems_filter module is kind of a bi... 😂
It keeps updating the ems filter on each run. then i started to analyze and i found that it also checkes how you enter the severities. i had it like that:
'ERROR,EMERGENCY,ALERT'
and it keep updating on each run on all our netapp clusters.
then we change the entries to this:
'EMERGENCY,ALERT,ERROR'
and now its correct. its not updating the clusters on each run.
i also didnt found that in the documentation that we need to keep care about the severity to have this kind of sorted.