Project

General

Profile

Bug #7281

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

Added by Dennis Cabooter almost 4 years ago. Updated over 1 year ago.

Status:
Released
Priority:
3
Category:
Web - Compliance & node report
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
58

Description

The title says it all. See attached screenshot.


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

Has duplicate Rudder - Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of complianceRejectedActions
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 complianceRejectedActions

Associated revisions

Revision 60df1cd7 (diff)
Added by François ARMAND over 1 year ago

Fixes #7281: Compliance keeps on loading while node is not online and \"last seen\" is not \"never\"

Revision 0cfabf0a (diff)
Added by François ARMAND over 1 year ago

Fixes #7281: Compliance keeps on loading while node is not online and \"last seen\" is not \"never\"

History

#1

Updated by Nicolas CHARLES almost 4 years ago

Dennis

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

#2

Updated by Dennis Cabooter almost 4 years ago

Neither. It's turning around forever.

#3

Updated by Florian Heigl over 3 years ago

i'll just add a screenshot.

My settings are:

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

#4

Updated by Benoît PECCATTE about 3 years ago

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

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 3.0.16 to 3.0.17
#6

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 3.0.17 to 302
#7

Updated by Alexis MOUSSET about 3 years ago

  • Target version changed from 302 to 3.1.12
#8

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 3.1.12 to 3.1.13
#9

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 3.1.13 to 3.1.14
#10

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 3.1.14 to 3.1.15
#11

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 3.1.15 to 3.1.16
#12

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 3.1.16 to 3.1.17
#13

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.17 to 3.1.18
#14

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.18 to 3.1.19
#15

Updated by Jonathan CLARKE over 2 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
#16

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Raphael GAUTHIER about 2 years ago

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

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.20 to 3.1.21
#19

Updated by Raphael GAUTHIER about 2 years ago

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

Updated by François ARMAND about 2 years ago

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

Updated by François ARMAND about 2 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
#22

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.21 to 3.1.22
#23

Updated by Benoît PECCATTE about 2 years ago

  • Priority changed from 45 to 58
#24

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.22 to 3.1.23
#25

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.23 to 3.1.24
#26

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.24 to 3.1.25
#27

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.25 to 387
#28

Updated by François ARMAND over 1 year ago

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

Updated by François ARMAND over 1 year 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
#30

Updated by François ARMAND over 1 year 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.

#31

Updated by François ARMAND over 1 year ago

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

Updated by François ARMAND over 1 year ago

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

Updated by François ARMAND over 1 year ago

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

Updated by François ARMAND over 1 year ago

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

Updated by François ARMAND over 1 year ago

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

Updated by François ARMAND over 1 year ago

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

Updated by François ARMAND over 1 year ago

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

Updated by François ARMAND over 1 year ago

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

Updated by Rudder Quality Assistant over 1 year ago

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

Updated by François ARMAND over 1 year ago

  • Status changed from Pending technical review to Pending release
#41

Updated by Vincent MEMBRÉ over 1 year 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.

Also available in: Atom PDF