Project

General

Profile

Actions

Bug #19545

closed

Warn sign in nodes list for disabled nodes

Added by Alexis Mousset over 2 years ago. Updated 10 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
37
Name check:
To do
Fix check:
To do
Regression:
No

Description

The compliance tabs are correct but the nodes list indicates a warning for system techniques while it should not.


Files


Related issues 1 (1 open0 closed)

Related to Rudder - Bug #8761: New nodes have compliance warning for system technique just after being addedNewActions
Actions #1

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.10 to 6.2.11
Actions #2

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.11 to 6.2.12
Actions #3

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.2.12 to 6.2.13
Actions #4

Updated by François ARMAND about 2 years ago

  • Related to Bug #8761: New nodes have compliance warning for system technique just after being added added
Actions #5

Updated by François ARMAND about 2 years ago

It may be a duplicate, or share root cause with #8761

Actions #6

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.13 to 6.2.14
Actions #7

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.14 to 6.2.15
Actions #8

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.2.15 to 6.2.16
Actions #9

Updated by Alexis Mousset over 1 year ago

  • Target version changed from 6.2.16 to 6.2.17
Actions #10

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.2.17 to 997
Actions #11

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 997 to 6.2.18
Actions #12

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.2.18 to 6.2.19
Actions #13

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.2.19 to 6.2.20
Actions #14

Updated by Vincent MEMBRÉ over 1 year ago

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

Updated by François ARMAND 10 months ago

this is now resolved in 7.2, we only have an info message that the node is disabled

Actions #16

Updated by Alexis Mousset 10 months ago

still there

Actions #17

Updated by François ARMAND 10 months ago

  • Target version changed from old 6.2 issues to relocate to 7.2.7
  • Severity set to Minor - inconvenience | misleading | easy workaround
  • UX impact set to It bothers me each time
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 37
Actions #18

Updated by François ARMAND 10 months ago

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

Updated by François ARMAND 10 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder/pull/4786
Actions #20

Updated by Anonymous 10 months ago

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

Updated by Vincent MEMBRÉ 10 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.2.7 and 7.3.2 which were released today.

Actions

Also available in: Atom PDF