Project

General

Profile

Bug #12649

Spinning compliance in nodes list on a disabled node

Added by Alexis MOUSSET over 1 year ago. Updated 12 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Priority:
0

Description

On 4.3.1, we have two ignored nodes: one has no compliance data, the other always keeps a spinning compliance wheel.


Subtasks

Bug #13840: By default, the list of nodes screen displays only one line in the table ReleasedFrançois ARMANDActions

Associated revisions

Revision f6fe2f28 (diff)
Added by Vincent MEMBRÉ 12 months ago

Fixes #12649: Spinning compliance in nodes list on a disabled node

Revision 1c55f964 (diff)
Added by Vincent MEMBRÉ 12 months ago

Fixes #12649: Spinning compliance in nodes list on a disabled node

History

#1

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.3.2 to 410
#2

Updated by Benoît PECCATTE over 1 year ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 32
#3

Updated by Benoît PECCATTE over 1 year ago

  • Target version changed from 410 to 4.3.2
#4

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.3.2 to 4.3.3
#5

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.3.3 to 4.3.4
#6

Updated by Benoît PECCATTE over 1 year ago

  • Target version changed from 4.3.4 to 4.3.5
#7

Updated by François ARMAND about 1 year ago

  • Effort required set to Very Small
  • Priority changed from 32 to 58

It should be just a check somewhere if compliance is missing, something like https://www.rudder-project.org/redmine/issues/7281

#8

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.3.5 to 4.3.6
  • Priority changed from 58 to 57
#9

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.3.6 to 4.3.7
#10

Updated by François ARMAND about 1 year ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
  • Priority changed from 57 to 0
#11

Updated by François ARMAND about 1 year ago

So in fact, it is not like #7281 which correctly correct the case when the node are not available.

Nodes on first page of the table get a "no data available".
But if the node compliance is not displayed on the first page of the table, then we get the spinning wheel.

#12

Updated by François ARMAND about 1 year ago

  • Status changed from In progress to New
  • Assignee deleted (François ARMAND)

OK, I don't know at all where to look. Perhaps Vincent or Raphaël cool take a look.

#13

Updated by Vincent MEMBRÉ 12 months ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
#14

Updated by Vincent MEMBRÉ 12 months ago

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

Updated by Vincent MEMBRÉ 12 months ago

  • Status changed from In progress to Pending technical review
  • Pull Request set to https://github.com/Normation/rudder/pull/2084
#16

Updated by Rudder Quality Assistant 12 months ago

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

Updated by Vincent MEMBRÉ 12 months ago

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

Updated by Vincent MEMBRÉ 12 months ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.7 and 5.0.3 which were released today.
Changelog
Changelog

Also available in: Atom PDF