Project

General

Profile

Actions
Copy link

Bug #17004

closed

multiple instance of a technique applied to a single node can lead to missing reports

Added by Tim Taler over 4 years ago. Updated 8 months ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
old 6.1 issues to relocate
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

I like to set sysctl variables through a technique and created therefore the attached technique (exported file attached).

This technique has to parameters: "var_name" and "var_val".
I use "File key-value present" to set this ke/vakue in /etc/sysctl.conf
and on the condition that this was repaired I use "Command execution"
to execute /sbin/sysctl -p

If I now apply this technique several times (with several directives, using each time another key/value pair)
all but the first command execution return a Messages --> "Missing" in version 6.0.4

I had the exact same technique in 5.0.15 and there it worked (all green)

Actions
Copy link
 #1

Updated by Alexis Mousset over 4 years ago

  • Category set to Techniques
Actions
Copy link
 #2

Updated by François ARMAND over 4 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 50
Actions
Copy link
 #3

Updated by François ARMAND over 4 years ago

  • Target version set to 6.0.8
  • Severity changed from Major - prevents use of part of Rudder | no simple workaround to Critical - prevents main use of Rudder | no workaround | data loss | security
  • Priority changed from 50 to 73

Upgrading to critical since it's a regression (and we missed it, sorry Tim)

Actions
Copy link
 #4

Updated by Nicolas CHARLES over 4 years ago

Hi Tim,

Do you know that we have a generic method sysctl exactly for this use case?

Cause of the issue here is that the command is the same for all directives, with exact same value, so it is executed only once, and then skipped (agent don't execute twice the same command :( )
Workaround: add a comment after the sysctl -p
like

sysctl -p # reload for variable ${var_name}

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.8 to 6.0.9
  • Priority changed from 73 to 72
Actions
Copy link
 #6

Updated by Nicolas CHARLES over 4 years ago

  • Priority changed from 72 to 71

Hi Tim,

Could you try to use sysctl generic method for this use case?

Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.9 to 6.0.10
  • Priority changed from 71 to 70
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.10 to 798
  • Priority changed from 70 to 69
Actions
Copy link
 #9

Updated by Benoît PECCATTE over 3 years ago

  • Target version changed from 798 to 6.1.14
  • Priority changed from 69 to 63
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions
Copy link
 #18

Updated by François ARMAND 8 months ago

  • Status changed from New to Rejected
  • Priority changed from 63 to 0
  • Regression set to No

Closing since no return from original author.

Actions
Copy link

Also available in: Atom PDF