Project

General

Profile

Actions

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
Category:
Web - Compliance & node report
Target version:
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 open4 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 #1

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.0.15 to 3.0.16
Actions #2

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.0.16 to 3.0.17
Actions #3

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.0.17 to 2.11.23
Actions #4

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.23 to 302
Actions #5

Updated by Alexis Mousset almost 8 years ago

  • Target version changed from 302 to 3.1.12
Actions #6

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions #7

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions #8

Updated by François ARMAND over 7 years ago

  • Related to Bug #7336: Node stuck in "Applying" status added
Actions #9

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #10

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #11

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #12

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #13

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #14

Updated by Jonathan CLARKE about 7 years ago

  • Related to Bug #8141: On rules creation, we may get a never stopping spining wheel on rules list added
Actions #15

Updated by Jonathan CLARKE about 7 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround

I'm not sure but this could be related to #8141.

Actions #16

Updated by Jonathan CLARKE almost 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
Actions #17

Updated by François ARMAND almost 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
Actions #18

Updated by François ARMAND almost 7 years ago

  • Assignee set to Raphael GAUTHIER
Actions #19

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #20

Updated by Jonathan CLARKE almost 7 years ago

  • Assignee deleted (Raphael GAUTHIER)
Actions #21

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #22

Updated by François ARMAND almost 7 years ago

  • Related to Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a rule added
Actions #23

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #24

Updated by Benoît PECCATTE almost 7 years ago

  • Priority changed from 37 to 46
Actions #25

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #26

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #27

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #28

Updated by Benoît PECCATTE over 6 years ago

  • Priority changed from 46 to 56
Actions #29

Updated by François ARMAND over 6 years ago

Actions #30

Updated by François ARMAND over 6 years ago

  • Related to deleted (User story #11810: Make node state configurable in node details)
Actions #31

Updated by François ARMAND over 6 years ago

  • Related to Bug #11842: Node in "ignored" state get a spinning wheel in place of compliance added
Actions #32

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.25 to 387
Actions #33

Updated by François ARMAND over 6 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #34

Updated by François ARMAND over 6 years ago

  • Target version changed from 387 to 4.1.10
Actions #35

Updated by François ARMAND over 6 years ago

  • Related to deleted (Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a rule)
Actions #36

Updated by François ARMAND over 6 years ago

  • Is duplicate of Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a rule added
Actions #37

Updated by François ARMAND over 6 years ago

  • Status changed from In progress to Rejected

Duplicates #7281

Actions

Also available in: Atom PDF