Actions
Bug #8030
closed
When a node doesn't have expected reports, we have a spinning wheel in place of compliance
Status:
Rejected
Priority:
3
Assignee:
Category:
Web - Compliance & node report
Target version:
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.
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.15 to 3.0.16
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.16 to 3.0.17
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.17 to 2.11.23
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.23 to 302
Updated by Alexis Mousset over 8 years ago
- Target version changed from 302 to 3.1.12
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.12 to 3.1.13
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.13 to 3.1.14
Updated by François ARMAND about 8 years ago
- Related to Bug #7336: Node stuck in "Applying" status added
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Jonathan CLARKE almost 8 years ago
- Related to Bug #8141: On rules creation, we may get a never stopping spining wheel on rules list added
Updated by Jonathan CLARKE almost 8 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
I'm not sure but this could be related to #8141.
Updated by Jonathan CLARKE over 7 years ago
- Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
- Priority set to 0
Updated by François ARMAND over 7 years ago
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Effort required set to Small
- Priority changed from 0 to 37
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Jonathan CLARKE over 7 years ago
- Assignee deleted (
Raphael GAUTHIER)
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by François ARMAND over 7 years ago
- Related to Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a rule added
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.21 to 3.1.22
Updated by
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.22 to 3.1.23
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.23 to 3.1.24
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.24 to 3.1.25
Updated by François ARMAND about 7 years ago
- Related to User story #11810: Make node state configurable in node details added
Updated by François ARMAND about 7 years ago
- Related to deleted (User story #11810: Make node state configurable in node details)
Updated by François ARMAND about 7 years ago
- Related to Bug #11842: Node in "ignored" state get a spinning wheel in place of compliance added
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.25 to 387
Updated by François ARMAND about 7 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 7 years ago
- Target version changed from 387 to 4.1.10
Updated by François ARMAND about 7 years ago
- Related to deleted (Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a rule)
Updated by François ARMAND about 7 years ago
- Is duplicate of Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a rule added
Updated by François ARMAND about 7 years ago
- Status changed from In progress to Rejected
Duplicates #7281
Actions