-
Problem report
-
Resolution: Fixed
-
Trivial
-
7.0.0alpha2
-
Sprint 101 (Jun 2023), Sprint 102 (Jul 2023), Sprint 103 (Aug 2023)
-
0.5
Precondition:
Master only (7.0.0alpha2)
Steps to reproduce:
- Create a discovery rule with e.g two unique SNMPv1 checks:
-) Port range for both checks ->161
-) SNMP community for both checks -> public
-) SNMP OID for first check -> iso.3.6.1.2.1.1.4.0; for second check ->iso.3.6.1.2.1.1.5.0 - Open newly created discovery rule
- Edit any SNMPv1 check
- Press the update button
Result: Validation error 'Check already exists.' appears. The same problem appears with updating SNMPv2 and SNMPv3 checks.
Please see the video attachment:
Expected: no validation error should appear because checks are unique in this case.
- caused by
-
ZBXNEXT-8275 Frontend changes for fping False Positive on Redirected Response
- Closed
-
ZBXNEXT-8386 Make Discovery configuration form modal
- Closed