Project

General

Profile

Bug #12262

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

Added by Alexis MOUSSET 9 months ago. Updated 7 months ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

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

Associated revisions

Revision dc565258 (diff)
Added by Alexis MOUSSET 7 months ago

Fixes #12262: jobScheduler does not work when the first non-loopback interface has no ip address

History

#2 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 4.1.11 to 4.1.12

#3 Updated by Alexis MOUSSET 7 months ago

  • Status changed from New to In progress
  • Assignee set to Alexis MOUSSET

#4 Updated by Alexis MOUSSET 7 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis MOUSSET to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1297

#5 Updated by Normation Quality Assistant 7 months ago

  • Assignee changed from Benoît PECCATTE to Alexis MOUSSET

#6 Updated by Alexis MOUSSET 7 months ago

  • Status changed from Pending technical review to Pending release

#7 Updated by Benoît PECCATTE 7 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.12, 4.2.6 and 4.3.1 which were released today.

Also available in: Atom PDF