Project

General

Profile

Actions
Copy link

Bug #7281

closed

Compliance keeps on loading while expected reports are not available for a node or a rule

Added by Dennis Cabooter about 9 years ago. Updated over 6 years ago.

Status:
Released
Priority:
3
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
4.1.10
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
58
Name check:
Fix check:
Regression:

Description

The title says it all. See attached screenshot.

Files

Download all files
Rudder-loading.png (56.7 KB) Rudder-loading.png Dennis Cabooter, 2015-10-15 16:04
rudder-forever-loading.png (6.66 KB) rudder-forever-loading.png Florian Heigl, 2015-10-21 16:46

Related issues 3 (0 open — 3 closed)

Has duplicate Rudder - Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of complianceRejectedFrançois ARMANDActions
Has duplicate Rudder - Bug #8141: On rules creation, we may get a never stopping spining wheel on rules listRejectedActions
Has duplicate Rudder - Bug #11842: Node in "ignored" state get a spinning wheel in place of complianceRejectedFrançois ARMANDActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES about 9 years ago

Dennis

Does it finally time out ? Or does it simply stall ?

Actions
Copy link
 #2

Updated by Dennis Cabooter about 9 years ago

Neither. It's turning around forever.

Actions
Copy link
 #3

Updated by Florian Heigl about 9 years ago

i'll just add a screenshot.

My settings are:

Compliance mode: Changes only.
Send heartbeat every: 1 runs.

Actions
Copy link
 #4

Updated by Benoît PECCATTE over 8 years ago

  • Category set to Web - UI & UX
  • Target version set to 3.0.16
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.16 to 3.0.17
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.17 to 302
Actions
Copy link
 #7

Updated by Alexis Mousset over 8 years ago

  • Target version changed from 302 to 3.1.12
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #15

Updated by Jonathan CLARKE over 7 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
  • Priority set to 0
Actions
Copy link
 #17

Updated by Raphael GAUTHIER over 7 years ago

  • Status changed from New to In progress
  • Assignee set to Raphael GAUTHIER
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions
Copy link
 #19

Updated by Raphael GAUTHIER over 7 years ago

  • Category changed from Web - UI & UX to Web - Compliance & node report
Actions
Copy link
 #20

Updated by François ARMAND over 7 years ago

  • Related to Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of compliance added
Actions
Copy link
 #21

Updated by François ARMAND over 7 years ago

  • User visibility changed from Operational - other Techniques | Technique editor | Rudder settings to Getting started - demo | first install | level 1 Techniques
  • Priority changed from 0 to 45
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions
Copy link
 #23

Updated by Benoît PECCATTE over 7 years ago

  • Priority changed from 45 to 58
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.25 to 387
Actions
Copy link
 #28

Updated by François ARMAND almost 7 years ago

  • Assignee changed from Raphael GAUTHIER to François ARMAND
  • Target version changed from 387 to 4.1.10
Actions
Copy link
 #29

Updated by François ARMAND almost 7 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1818
Actions
Copy link
 #30

Updated by François ARMAND almost 7 years ago

  • Subject changed from Compliance keeps on loading while node is not online and "last seen" is not "never" to Compliance keeps on loading while expected reports are not available for a node or a rule

Updating the message to make it clear that the problem is both on nodes and rules.

Actions
Copy link
 #31

Updated by François ARMAND almost 7 years ago

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

Updated by François ARMAND almost 7 years ago

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

Updated by François ARMAND almost 7 years ago

  • Related to deleted (Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of compliance)
Actions
Copy link
 #34

Updated by François ARMAND almost 7 years ago

  • Related to deleted (Bug #8141: On rules creation, we may get a never stopping spining wheel on rules list)
Actions
Copy link
 #35

Updated by François ARMAND almost 7 years ago

  • Related to deleted (Bug #11842: Node in "ignored" state get a spinning wheel in place of compliance)
Actions
Copy link
 #36

Updated by François ARMAND almost 7 years ago

  • Has duplicate Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of compliance added
Actions
Copy link
 #37

Updated by François ARMAND almost 7 years ago

  • Has duplicate Bug #8141: On rules creation, we may get a never stopping spining wheel on rules list added
Actions
Copy link
 #38

Updated by François ARMAND almost 7 years ago

  • Has duplicate Bug #11842: Node in "ignored" state get a spinning wheel in place of compliance added
Actions
Copy link
 #39

Updated by Rudder Quality Assistant almost 7 years ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND
Actions
Copy link
 #40

Updated by François ARMAND almost 7 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #41

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.10 and 4.2.4 which were released today.

Actions
Copy link

Also available in: Atom PDF