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

Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a rule

Added by Dennis Cabooter over 10 years ago. Updated about 8 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
Rudder-loading.png
rudder-forever-loading.png

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

Updated by Nicolas CHARLES over 10 years ago Actions
Copy link
 #1

Dennis

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

Updated by Dennis Cabooter over 10 years ago Actions
Copy link
 #2

Neither. It's turning around forever.

Updated by Florian Heigl over 10 years ago Actions
Copy link
 #3

rudder-forever-loading.png

i'll just add a screenshot.

My settings are:

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

Updated by Benoît PECCATTE almost 10 years ago Actions
Copy link
 #4

  • Category set to Web - UI & UX
  • Target version set to 3.0.16

Updated by Vincent MEMBRÉ almost 10 years ago Actions
Copy link
 #5

  • Target version changed from 3.0.16 to 3.0.17

Updated by Vincent MEMBRÉ almost 10 years ago Actions
Copy link
 #6

  • Target version changed from 3.0.17 to 302

Updated by Alexis Mousset over 9 years ago Actions
Copy link
 #7

  • Target version changed from 302 to 3.1.12

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #8

  • Target version changed from 3.1.12 to 3.1.13

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #9

  • Target version changed from 3.1.13 to 3.1.14

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #10

  • Target version changed from 3.1.14 to 3.1.15

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #11

  • Target version changed from 3.1.15 to 3.1.16

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #12

  • Target version changed from 3.1.16 to 3.1.17

Updated by Vincent MEMBRÉ over 9 years ago Actions
Copy link
 #13

  • Target version changed from 3.1.17 to 3.1.18

Updated by Vincent MEMBRÉ about 9 years ago Actions
Copy link
 #14

  • Target version changed from 3.1.18 to 3.1.19

Updated by Jonathan CLARKE almost 9 years ago Actions
Copy link
 #15

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

Updated by Vincent MEMBRÉ almost 9 years ago Actions
Copy link
 #16

  • Target version changed from 3.1.19 to 3.1.20
  • Priority set to 0

Updated by Raphael GAUTHIER almost 9 years ago Actions
Copy link
 #17

  • Status changed from New to In progress
  • Assignee set to Raphael GAUTHIER

Updated by Vincent MEMBRÉ almost 9 years ago Actions
Copy link
 #18

  • Target version changed from 3.1.20 to 3.1.21

Updated by Raphael GAUTHIER almost 9 years ago Actions
Copy link
 #19

  • Category changed from Web - UI & UX to Web - Compliance & node report

Updated by François ARMAND over 8 years ago Actions
Copy link
 #20

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

Updated by François ARMAND over 8 years ago Actions
Copy link
 #21

  • 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

Updated by Vincent MEMBRÉ over 8 years ago Actions
Copy link
 #22

  • Target version changed from 3.1.21 to 3.1.22

Updated by Benoît PECCATTE over 8 years ago Actions
Copy link
 #23

  • Priority changed from 45 to 58

Updated by Vincent MEMBRÉ over 8 years ago Actions
Copy link
 #24

  • Target version changed from 3.1.22 to 3.1.23

Updated by Vincent MEMBRÉ over 8 years ago Actions
Copy link
 #25

  • Target version changed from 3.1.23 to 3.1.24

Updated by Vincent MEMBRÉ over 8 years ago Actions
Copy link
 #26

  • Target version changed from 3.1.24 to 3.1.25

Updated by Vincent MEMBRÉ over 8 years ago Actions
Copy link
 #27

  • Target version changed from 3.1.25 to 387

Updated by François ARMAND about 8 years ago Actions
Copy link
 #28

  • Assignee changed from Raphael GAUTHIER to François ARMAND
  • Target version changed from 387 to 4.1.10

Updated by François ARMAND about 8 years ago Actions
Copy link
 #29

  • 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

Updated by François ARMAND about 8 years ago Actions
Copy link
 #30

  • 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.

Updated by François ARMAND about 8 years ago Actions
Copy link
 #31

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

Updated by François ARMAND about 8 years ago Actions
Copy link
 #32

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

Updated by François ARMAND about 8 years ago Actions
Copy link
 #33

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

Updated by François ARMAND about 8 years ago Actions
Copy link
 #34

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

Updated by François ARMAND about 8 years ago Actions
Copy link
 #35

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

Updated by François ARMAND about 8 years ago Actions
Copy link
 #36

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

Updated by François ARMAND about 8 years ago Actions
Copy link
 #37

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

Updated by François ARMAND about 8 years ago Actions
Copy link
 #38

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

Updated by Rudder Quality Assistant about 8 years ago Actions
Copy link
 #39

  • Assignee changed from Vincent MEMBRÉ to François ARMAND

Updated by François ARMAND about 8 years ago Actions
Copy link
 #40

  • Status changed from Pending technical review to Pending release

Updated by Vincent MEMBRÉ about 8 years ago Actions
Copy link
 #41

  • 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: PDF Atom