Bug #12649: Spinning compliance in nodes list on a disabled node - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
CS - by priority
CS - to review
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

Bug #12649

closed

Spinning compliance in nodes list on a disabled node

Added by Alexis Mousset over 6 years ago. Updated almost 6 years ago.

Status:

Released

Priority:

N/A

Assignee:

Vincent MEMBRÉ

Category:

Web - Config management

Target version:

4.3.7

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Operational - other Techniques | Technique editor | Rudder settings

Effort required:

Very Small

Priority:

Name check:

Fix check:

Regression:

Description

On 4.3.1, we have two ignored nodes: one has no compliance data, the other always keeps a spinning compliance wheel.

Subtasks 1 (0 open — 1 closed)

Bug #13840: By default, the list of nodes screen displays only one line in the table

Released

François ARMAND

Actions

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Vincent MEMBRÉ over 6 years ago

Target version changed from 4.3.2 to 410

Actions

Copy link

Updated by Benoît PECCATTE over 6 years ago

Severity set to Minor - inconvenience | misleading | easy workaround
User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Priority changed from 0 to 32

Actions

Copy link

Updated by Benoît PECCATTE over 6 years ago

Target version changed from 410 to 4.3.2

Actions

Copy link

Updated by Vincent MEMBRÉ over 6 years ago

Target version changed from 4.3.2 to 4.3.3

Actions

Copy link

Updated by Vincent MEMBRÉ over 6 years ago

Target version changed from 4.3.3 to 4.3.4

Actions

Copy link

Updated by Benoît PECCATTE over 6 years ago

Target version changed from 4.3.4 to 4.3.5

Actions

Copy link

Updated by François ARMAND about 6 years ago

Effort required set to Very Small
Priority changed from 32 to 58

It should be just a check somewhere if compliance is missing, something like https://www.rudder-project.org/redmine/issues/7281

Actions

Copy link

Updated by Vincent MEMBRÉ about 6 years ago

Target version changed from 4.3.5 to 4.3.6
Priority changed from 58 to 57

Actions

Copy link

Updated by Vincent MEMBRÉ about 6 years ago

Target version changed from 4.3.6 to 4.3.7

Actions

Copy link

#10

Updated by François ARMAND about 6 years ago

Status changed from New to In progress
Assignee set to François ARMAND
Priority changed from 57 to 0

Actions

Copy link

#11

Updated by François ARMAND about 6 years ago

So in fact, it is not like #7281 which correctly correct the case when the node are not available.

Nodes on first page of the table get a "no data available".
But if the node compliance is not displayed on the first page of the table, then we get the spinning wheel.

Actions

Copy link

#12