Project

General

Profile

Bug #12137

Missing "update" reports on node

Added by Nicolas CHARLES over 1 year ago. Updated 5 months ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
69
Tags:

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

Related to Rudder - Bug #10423: Random missing "update" reports on RelayNewActions

Associated revisions

Revision 96ff6712 (diff)
Added by Nicolas CHARLES 7 months ago

Fixes #12137: Missing \"update\" reports on node

History

#1

Updated by Nicolas CHARLES over 1 year ago

  • Related to Bug #10423: Random missing "update" reports on Relay added
#2

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.10 to 4.1.11
#3

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.11 to 4.1.12
#4

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.12 to 4.1.13
#5

Updated by Benoît PECCATTE over 1 year ago

  • Target version changed from 4.1.13 to 411
#6

Updated by Benoît PECCATTE over 1 year ago

  • Target version changed from 411 to 4.1.13
#7

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.1.13 to 4.1.14
#8

Updated by François ARMAND about 1 year 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
#9

Updated by Benoît PECCATTE about 1 year ago

  • Target version changed from 4.1.14 to 4.1.15
#10

Updated by Vincent MEMBRÉ 11 months ago

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

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 4.1.16 to 4.1.17
#12

Updated by Vincent MEMBRÉ 10 months ago

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

Updated by François ARMAND 9 months ago

  • Tags 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
#14

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 4.1.18 to 4.1.19
#15

Updated by François ARMAND 9 months ago

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

Updated by François ARMAND 9 months ago

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

Updated by François ARMAND 9 months ago

  • Description updated (diff)
#18

Updated by François ARMAND 8 months 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).

#19

Updated by Alexis MOUSSET 8 months ago

  • Target version changed from 4.3.9 to 4.3.10
#20

Updated by François ARMAND 7 months 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).

#21

Updated by Nicolas CHARLES 7 months ago

  • Status changed from New to In progress
#22

Updated by Nicolas CHARLES 7 months ago

this looks to be the way it works (fails)

#23

Updated by Nicolas CHARLES 7 months 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
#24

Updated by Rudder Quality Assistant 7 months ago

  • Assignee changed from Alexis MOUSSET to Nicolas CHARLES
#25

Updated by Nicolas CHARLES 7 months ago

  • Status changed from Pending technical review to Pending release
#26

Updated by François ARMAND 7 months ago

  • Target version changed from 4.3.10 to 4.3.11
#27

Updated by Vincent MEMBRÉ 5 months 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.

Also available in: Atom PDF