Project

General

Profile

Actions

Bug #19258

closed

Pending nodes History Tab shows duplicate entries

Added by Lars Koenen almost 3 years ago. Updated 11 months ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
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:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

When i accept a new node, it is shown twice in the history tab afterwards.
Refused nodes only show once.

Rudder Version is 6.2.6

Actions #1

Updated by Elaad FURREEDAN almost 3 years ago

  • Assignee set to Elaad FURREEDAN

Thank you for the report !
I was able to reproduce it, I will work on it

Actions #2

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.2.7 to 6.2.8
Actions #3

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.8 to 6.2.9
Actions #4

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.9 to 6.2.10
  • Priority changed from 50 to 49
Actions #5

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.10 to 6.2.11
  • Priority changed from 49 to 48
Actions #6

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.11 to 6.2.12
  • Priority changed from 48 to 47
Actions #7

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.12 to 6.2.13
  • Priority changed from 47 to 46
Actions #8

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.13 to 6.2.14
  • Priority changed from 46 to 43
Actions #9

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.14 to 6.2.15
  • Priority changed from 43 to 42
Actions #10

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.15 to 6.2.16
Actions #11

Updated by Alexis Mousset over 1 year ago

  • Target version changed from 6.2.16 to 6.2.17
Actions #12

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.2.17 to 997
  • Priority changed from 42 to 0
Actions #13

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 997 to 6.2.18
Actions #14

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.2.18 to 6.2.19
Actions #15

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.2.19 to 6.2.20
Actions #16

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.2.20 to old 6.2 issues to relocate
Actions #17

Updated by Elaad FURREEDAN 12 months ago

  • Status changed from New to In progress
Actions #18

Updated by Elaad FURREEDAN 12 months ago

  • Status changed from In progress to New
  • Target version changed from old 6.2 issues to relocate to 7.2.6
  • Regression set to No
Actions #19

Updated by Elaad FURREEDAN 12 months ago

  • Status changed from New to In progress
Actions #20

Updated by Elaad FURREEDAN 12 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Elaad FURREEDAN to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/4741
Actions #21

Updated by Anonymous 12 months ago

  • Status changed from Pending technical review to Pending release
Actions #22

Updated by Vincent MEMBRÉ 11 months ago

  • Fix check changed from To do to Checked
Actions #23

Updated by Vincent MEMBRÉ 11 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.2.6 and 7.3.1 which were released today.

Actions

Also available in: Atom PDF