You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In filter expressions, zabbix_action.py still references the proxyname as host, where Zabbix 7.0 now expects the proxyname to be referenced as name (see https://www.zabbix.com/documentation/current/en/manual/api/changes, specifically api changes related to ZBXNEXT-8500)
This causes community.zabbix.zabbix_action to fail whenever it tries to lookup zabbix proxy details.
Changing "filter": {"host": [proxy_name]} to "filter": {"name": [proxy_name]} in zabbix_action.py (line 1018) "fixes" the issue
SUMMARY
In filter expressions, zabbix_action.py still references the proxyname as host, where Zabbix 7.0 now expects the proxyname to be referenced as name (see https://www.zabbix.com/documentation/current/en/manual/api/changes, specifically api changes related to ZBXNEXT-8500)
This causes community.zabbix.zabbix_action to fail whenever it tries to lookup zabbix proxy details.
Changing
"filter": {"host": [proxy_name]}
to"filter": {"name": [proxy_name]}
in zabbix_action.py (line 1018) "fixes" the issueISSUE TYPE
COMPONENT NAME
zabbix_action.py
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT / Zabbix Version
AlmaLinux 9
Zabbix 7.0
STEPS TO REPRODUCE
Use the community.zabbix.zabbix_action module to add an autoregistration action (based on zabbix_proxy)
EXPECTED RESULTS
The play succeeds
ACTUAL RESULTS
The play fails
The text was updated successfully, but these errors were encountered: