Project

General

Profile

Actions
Copy link

Bug #8030

closed

When a node doesn't have expected reports, we have a spinning wheel in place of compliance

Added by François ARMAND about 8 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
3
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
4.1.10
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Priority:
56
Name check:
Fix check:
Regression:

Description

When a node doesn't have compliance, we get the loading spinning wheel in place of something useful.

It seems that in that case, the "useful" thing would be an error message explaining what is happening for that node.

It happens in 3.1 and perhaps in 3.0 to.

Related issues 4 (0 open — 4 closed)

Related to Rudder - Bug #7336: Node stuck in "Applying" statusRejectedFrançois ARMANDActions
Related to Rudder - Bug #8141: On rules creation, we may get a never stopping spining wheel on rules listRejectedActions
Related to Rudder - Bug #11842: Node in "ignored" state get a spinning wheel in place of complianceRejectedFrançois ARMANDActions
Is duplicate of Rudder - Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a ruleReleasedFrançois ARMANDActions
Actions
Copy link

Also available in: Atom PDF