Project

General

Profile

Actions

Bug #4193

closed

Rudder 2.6.8: In 'Confiiguration Policy - Rules' screen: 'Unknown' state in a Rule will be displayed at the end instead of the begining of the Directives list

Added by Nicolas PERRON over 10 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
2
Assignee:
-
Category:
-
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

With Rudder 2.6.8, if a Rule is in 'Unknown' state, we have to show the latest Directives to known which one has 'Unknown' status.
This is disturbing as when you see that a node is not compliant, you have to search where are Directives which are not in 'Success'.

Actions #1

Updated by Nicolas CHARLES over 10 years ago

Could you explain what you expected ?
What is the "latest" ?

When your rule is in unknown, the main way to see what is wrong is to click on it to see the compliances details, where you have all the Directives displayed with their status

Actions #2

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.6.10 to 2.6.11
Actions #3

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.11 to 2.6.12
Actions #4

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.12 to 2.6.13
Actions #5

Updated by Nicolas PERRON almost 10 years ago

What I mean is that if a Rule contains a Directive in an "unknown state", this Directive will be at the end of the list by default. Then, to know what is the problem we have to click twice on the column 'Status' to show the incriminated Directive.

Actions #6

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.6.13 to 2.6.14
Actions #7

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.14 to 2.6.16
Actions #8

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.16 to 2.6.17
Actions #9

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.6.17 to 2.6.18
Actions #10

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 2.6.18 to 2.6.19
Actions #11

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.6.19 to 2.6.20
Actions #12

Updated by François ARMAND about 9 years ago

  • Status changed from New to Rejected
  • Target version changed from 2.6.20 to 2.10.10

Sorting was modified in 2.10.

Actions

Also available in: Atom PDF