Project

General

Profile

Actions

Bug #12137

closed

Missing "update" reports on node

Bug #12137: Missing "update" reports on node

Added by Nicolas CHARLES almost 8 years ago. Updated over 3 years ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
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 open1 closed)

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

Updated by Nicolas CHARLES almost 8 years ago Actions #1

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

Updated by Vincent MEMBRÉ almost 8 years ago Actions #2

  • Target version changed from 4.1.10 to 4.1.11

Updated by Vincent MEMBRÉ over 7 years ago Actions #3

  • Target version changed from 4.1.11 to 4.1.12

Updated by Vincent MEMBRÉ over 7 years ago Actions #4

  • Target version changed from 4.1.12 to 4.1.13

Updated by Benoît PECCATTE over 7 years ago Actions #5

  • Target version changed from 4.1.13 to 411

Updated by Benoît PECCATTE over 7 years ago Actions #6

  • Target version changed from 411 to 4.1.13

Updated by Vincent MEMBRÉ over 7 years ago Actions #7

  • Target version changed from 4.1.13 to 4.1.14

Updated by François ARMAND over 7 years ago Actions #8

  • 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

Updated by Benoît PECCATTE over 7 years ago Actions #9

  • Target version changed from 4.1.14 to 4.1.15

Updated by Vincent MEMBRÉ about 7 years ago Actions #10

  • Target version changed from 4.1.15 to 4.1.16
  • Priority changed from 47 to 45

Updated by Vincent MEMBRÉ about 7 years ago Actions #11

  • Target version changed from 4.1.16 to 4.1.17

Updated by Vincent MEMBRÉ about 7 years ago Actions #12

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 45 to 0

Updated by François ARMAND about 7 years ago Actions #13

  • 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

Updated by Vincent MEMBRÉ about 7 years ago Actions #14

  • Target version changed from 4.1.18 to 4.1.19

Updated by François ARMAND about 7 years ago Actions #15

  • Status changed from New to In progress
  • Assignee set to François ARMAND

Updated by François ARMAND about 7 years ago Actions #16

  • Status changed from In progress to New
  • Assignee deleted (François ARMAND)

Updated by François ARMAND about 7 years ago Actions #17

  • Description updated (diff)

Updated by François ARMAND almost 7 years ago Actions #18

  • 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).

Updated by Alexis Mousset almost 7 years ago Actions #19

  • Target version changed from 4.3.9 to 4.3.10

Updated by François ARMAND almost 7 years ago Actions #20

  • 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).

Updated by Nicolas CHARLES almost 7 years ago Actions #21

  • Status changed from New to In progress

Updated by Nicolas CHARLES almost 7 years ago Actions #22

this looks to be the way it works (fails)

Updated by Nicolas CHARLES almost 7 years ago Actions #23

  • 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

Updated by Rudder Quality Assistant almost 7 years ago Actions #24

  • Assignee changed from Alexis Mousset to Nicolas CHARLES

Updated by Nicolas CHARLES almost 7 years ago Actions #25

  • Status changed from Pending technical review to Pending release

Updated by François ARMAND almost 7 years ago Actions #26

  • Target version changed from 4.3.10 to 4.3.11

Updated by Vincent MEMBRÉ over 6 years ago Actions #27

  • 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.

Updated by Alexis Mousset over 3 years ago Actions #28

  • Priority changed from 69 to 78
Actions

Also available in: PDF Atom