Project

General

Profile

Actions

Bug #12262

closed

jobScheduler does not work when the first non-loopback interface has no ip address

Added by Alexis Mousset almost 6 years ago. Updated almost 6 years ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Because the used splayclass is ${sys.host}${sys.ipv4} and sys.ipv4 is not defined when the first non-loopback interface has no IP address, the class triggerring the execution is never defined.

We can change this to hostname only as a workaround.

We also need to:

  • Fix the interfaces parsing to take the first available IP and avoid stopping after the first interface having no defined address
  • Add logs for splayclass to know at anytime what is the defined class in verbose logs
  • More generally add logs when promises containing undefined variables are skipped
Actions

Also available in: Atom PDF