HEAT Discovery tasks are stuck in pending after changing the Gateway Client Task Subnets to a long form IP address format

Version 1

    Details

    HEAT Discovery tasks are stuck in pending after changing the Gateway Client Task Subnets to a long form IP address format.


    After review of the C:\Program Files (x86)\Common Files\FRS\Logs\JobQueues\JobQueue_GetClientTasksQueue_AGG.log normally an error stating:  

    Error: "Server error: Invalid IP-range [IP Range]: An invalid IP address was specified."

     


    Resolution

    After review of the C:\Program Files (x86)\Common Files\FRS\Logs\JobQueues\JobQueue_GetClientTasksQueue_AGG.log normally an error stating:  


    Error: "Server error: Invalid IP-range [IP Range]: An invalid IP address was specified."

    This issue is normally due to an invalid range or use of a full 32-bit IP address range such as:

    001.001.001.001-001.001.001.254.

    HEAT Requires simple IP address formats for CI and Gateway entries such as:

    1.1.1.1-1.1.1.254