Details
-
Type:
Problem report
-
Status: Closed
-
Priority:
Trivial
-
Resolution: Fixed
-
Affects Version/s: 5.2.0alpha1
-
Fix Version/s: 4.0.25rc1, 5.0.4rc1, 5.2.0alpha2, 5.2 (plan)
-
Component/s: Frontend (F)
-
Labels:
-
Environment:Zabbix from master, Linux
-
Team:Team B
-
Sprint:Sprint 66 (Jul 2020), Sprint 67 (Aug 2020)
-
Story Points:2
Description
Steps to reproduce:
- On a fresh system, add host Master, add a discovery rule of type trapper, add a host prototype to the rule (host with the name and host group as LLD macros):
- Export Master host to an XML file.
- Send the JSON to the discovery rule:
{ "request": "sender data", "data": [ { "{#GOOD.HOSTNAME}": "good.host1", "{#GOOD.HOSTGROUP}": "good.hostgroup1" }, { "{#GOOD.HOSTNAME}": "good.host2", "{#GOOD.HOSTGROUP}": "good.hostgroup2" } ] }
- Observe that there are two hosts - good.host1 (belongs to group good.hostgroup1) and good.host2 (belongs to group good.hostgroup2).
- Import previously exported Master host; leave all options default
Result:
Both discovered groups good.hostgroup1, good.hostgroup2 have gone while discovered hosts good.host1, good.host2 are still present
Expected:
If there are no changes to the discovery rules of the imported host then all discovered entities must stay untouched.