Actions
Bug #19545
closedWarn sign in nodes list for disabled nodes
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
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
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.10 to 6.2.11
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.2.11 to 6.2.12
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.2.12 to 6.2.13
Updated by François ARMAND almost 3 years ago
- Related to Bug #8761: New nodes have compliance warning for system technique just after being added added
Updated by François ARMAND almost 3 years ago
It may be a duplicate, or share root cause with #8761
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.13 to 6.2.14
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.14 to 6.2.15
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.15 to 6.2.16
Updated by Alexis Mousset over 2 years ago
- Target version changed from 6.2.16 to 6.2.17
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.17 to 997
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 997 to 6.2.18
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.18 to 6.2.19
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.2.19 to 6.2.20
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 6.2.20 to old 6.2 issues to relocate
Updated by François ARMAND over 1 year ago
- File clipboard-202305041829-en8zt.png clipboard-202305041829-en8zt.png added
- Status changed from New to Resolved
- Regression set to No
this is now resolved in 7.2, we only have an info message that the node is disabled
Updated by Alexis Mousset over 1 year ago
- File clipboard-202305041832-im3di.png clipboard-202305041832-im3di.png added
- Status changed from Resolved to New
still there
Updated by François ARMAND over 1 year 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
Updated by François ARMAND over 1 year ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND over 1 year 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
Updated by Anonymous over 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|7041a470cd1244491b6bc9ca1b23887a66c98a0d.
Updated by Vincent MEMBRÉ over 1 year 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