HTTPClassyProbe does not create service affinity records (ip_service_affinity) - Known Error

HTTPClassyProbe does not create service affinity records (ip_service_affinity) Description On successful classification with HTTPClassyProbe, no ip_service_affinity record is created. Often, this results in running several very slow failing classification probes every time the IP is discovered.

Steps to Reproduce

Set sys_property glide.discovery.ip_service_affinity to true Discover a CI that responds to multiple classifications [ssh, snmp, etc] AND http Repeat this discovery Examine the ip_service_affinity table to see if a record has been created for the relevant IP address. You will find that it has not. Examine the second discovery status. Only HTTP classification should run, but you will see the other classifications attempted as well before HTTP Workaround This problem has been fixed. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to.