Discovery action continues to process old IP ranges after rule modification
Hello there,
We are experiencing an issue with Zabbix network discovery rules (Zabbix version: 7.0.29).
We use discovery rules to automatically create hosts within specific IP ranges. When we modify a discovery rule and replace its IP range with a new one, Zabbix continues to discover and create hosts from the old IP range, even though that range is no longer configured in the rule.
To work around the issue, we created a cleanup action that removes hosts that do not belong to the new IP range. However, this results in a loop: the hosts are deleted by the cleanup process and then recreated again by discovery shortly afterward.
From our observations, it appears that the discovery process continues to scan both the old and the new IP ranges after the rule has been modified. The only successful workaround we have found so far is to completely delete the discovery rule and its associated actions, then recreate them from scratch using the new IP range.
We would like to understand what could cause Zabbix to continue discovering hosts from IP ranges that are no longer configured and whether there is any cache, proxy data, or discovery-related information that needs to be cleared after modifying a discovery rule.
Our environment includes a Zabbix proxy performing the discovery scans, which may be relevant to the issue.
Thanks in advance for you assistance,
Eddie
We are experiencing an issue with Zabbix network discovery rules (Zabbix version: 7.0.29).
We use discovery rules to automatically create hosts within specific IP ranges. When we modify a discovery rule and replace its IP range with a new one, Zabbix continues to discover and create hosts from the old IP range, even though that range is no longer configured in the rule.
To work around the issue, we created a cleanup action that removes hosts that do not belong to the new IP range. However, this results in a loop: the hosts are deleted by the cleanup process and then recreated again by discovery shortly afterward.
From our observations, it appears that the discovery process continues to scan both the old and the new IP ranges after the rule has been modified. The only successful workaround we have found so far is to completely delete the discovery rule and its associated actions, then recreate them from scratch using the new IP range.
We would like to understand what could cause Zabbix to continue discovering hosts from IP ranges that are no longer configured and whether there is any cache, proxy data, or discovery-related information that needs to be cleared after modifying a discovery rule.
Our environment includes a Zabbix proxy performing the discovery scans, which may be relevant to the issue.
Thanks in advance for you assistance,
Eddie