-
Incident report
-
Resolution: Won't fix
-
Trivial
-
None
-
4.4.7
-
None
-
Centos 7, Zabbix 4.4.7, MariaDB 10.2
Steps to reproduce:
I'm not sure about the way to reproduce the issue. I have an old template coming from Zabbix 2.2. 'Template OS Linux'. On this template, some triggers are of type 7.
- Get an old template without Event Problem Generation option selected
- Select and export template
- Error 'Invalid tag "type": unexpected constant value "7"'
- Repeat operation with API configuration.export
- Same 'Invalid tag "type": unexpected constant value "7"'
- Repeat operation with API
template.get(templateids=10001,
output='extend',
selectTags='extend',
selectTemplates='extend',
selectParentTemplates='extend',
selectHttpTests='extend',
selectItems='extend',
selectDiscoveries='extend',
selectTriggers='extend',
selectGraphs='extend',
selectApplications='extend',
selectMacros='extend',
selectScreens='extend')
Result:
{{Exemple of trigger coming from api template.get {'triggerid': '13243', 'expression': '
{193603}>60', 'description': 'Disk I/O is overloaded on {HOST.NAME}', 'url': '', 'status': '0', 'value': '0', 'priority': '2', 'lastchange': '0', 'comments': 'OS spends significant time waiting for I/O (input/output) operations. It could be indicator of performance issues with storage system.', 'error': '', 'templateid': '0', 'type': '0', 'state': '0', 'flags': '0', 'recovery_mode': '0', 'recovery_expression': '', 'correlation_mode': '0', 'correlation_tag': '', 'manual_close': '1', 'opdata': ''}}}
Expected:
Trigger type should always be 0 or 1. All non 1 value in database should be changed to 0