F5 discovery errorDescriptionF5 discovery return error in patternFailed Exploring CI Pattern, Pattern name: F5 Load Balancer, To Check Pattern Log Press HereCheck For Output Payload Errors2021-03-23 15:03:28: Identification CI Errors:Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to other errors.,Update failed with error: commit failed or was not attempted due to otheSteps to Reproduce run discovery to F5WorkaroundProblem with the F5 Cluster the relation was Parent --> node // child--> cluster this looks incorrect it should be Parent --> cluster // child --> node. This needs to be fixed on step that creates the relation on step 1.15. Ref\Rel between cluster node and cluster. Just simply change the places between parent and child or apply attached pattern. This behavior could not be reproduced on a base instance (out-of-the-box). It could be due to customization, a missed upgrade on a particular instance, or a not fully known or documented design. If you are experiencing this problem, contact ServiceNow Technical Support.Related Problem: PRB1485415