Project

General

Profile

Actions
Copy link

Bug #12137

closed

Missing "update" reports on node

Added by Nicolas CHARLES almost 7 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
System techniques
Target version:
4.3.11
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
78
Name check:
Fix check:
Regression:

Description

After creating a technique in technique editor, one of my node had a missing update report.
I may, or may not be linked

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #10423: Missing "update" reports on Relay in rare casesRejectedActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 7 years ago

  • Related to Bug #10423: Missing "update" reports on Relay in rare cases added
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions
Copy link
 #5

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 4.1.13 to 411
Actions
Copy link
 #6

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 411 to 4.1.13
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions
Copy link
 #8

Updated by François ARMAND over 6 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques
  • Priority changed from 0 to 47
Actions
Copy link
 #9

Updated by Benoît PECCATTE over 6 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.15 to 4.1.16
  • Priority changed from 47 to 45
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 45 to 0
Actions
Copy link
 #13

Updated by François ARMAND almost 6 years ago

  • Translation missing: en.field_tag_list set to Sponsored
  • User visibility changed from Getting started - demo | first install | level 1 Techniques to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Priority changed from 0 to 71
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.18 to 4.1.19
Actions
Copy link
 #15

Updated by François ARMAND almost 6 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions
Copy link
 #16

Updated by François ARMAND almost 6 years ago

  • Status changed from In progress to New
  • Assignee deleted (François ARMAND)
Actions
Copy link
 #17

Updated by François ARMAND almost 6 years ago

  • Description updated (diff)
Actions
Copy link
 #18

Updated by François ARMAND almost 6 years ago

  • Target version changed from 4.1.19 to 4.3.9
  • Priority changed from 71 to 70

It won't be corrected in 4.1, too many things changed.
The first step which would help a lot is to find a process to reproduce it. It may be an interaction between ncf/technique editor (most likely hash ncf updated on technique creation but not correctly propagated).

Actions
Copy link
 #19

Updated by Alexis Mousset almost 6 years ago

  • Target version changed from 4.3.9 to 4.3.10
Actions
Copy link
 #20

Updated by François ARMAND almost 6 years ago

  • Assignee set to Nicolas CHARLES
  • Priority changed from 70 to 69

We have a new hypothesis:

- change on technique editor,
- change on ncf,
- but the update is on several step,
- so if the ncf hash is updated but not yet the policies, perhaps we miss that case (because nothing to change, so no outcome, no change, no update).

Actions
Copy link
 #21

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from New to In progress
Actions
Copy link
 #22

Updated by Nicolas CHARLES almost 6 years ago

this looks to be the way it works (fails)

Actions
Copy link
 #23

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1422
Actions
Copy link
 #24

Updated by Rudder Quality Assistant almost 6 years ago

  • Assignee changed from Alexis Mousset to Nicolas CHARLES
Actions
Copy link
 #25

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #26

Updated by François ARMAND almost 6 years ago

  • Target version changed from 4.3.10 to 4.3.11
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.3.11 and 5.0.9 which were released today.

Actions
Copy link
 #28

Updated by Alexis Mousset over 2 years ago

  • Priority changed from 69 to 78
Actions
Copy link

Also available in: Atom PDF