Project

General

Profile

Actions

Bug #19374

closed

API shows only part of the memory information

Added by Lars Koenen almost 3 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Category:
API
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
32
Name check:
To do
Fix check:
Checked
Regression:

Description

When I ask the API for details about the memory modules, I only get details about slotNumber, description and serialNumber

"memories": [
          {
            "slotNumber": "2" 
          },
          {
            "slotNumber": "1",
            "description": "DIMM",
            "serialNumber": "XXXXXXXX" 
          },
          {
            "slotNumber": "4" 
          },
          {
            "slotNumber": "3",
            "description": "DIMM",
            "serialNumber": "YYYYYYYY" 
          }
        ],

Rudder Version is 6.2.7

Actions #1

Updated by François ARMAND almost 3 years ago

Hello,

Do you have all the correct information for that node in the UI?

Actions #2

Updated by Lars Koenen almost 3 years ago

Yes, the WebUI shows me all the information.

Actions #3

Updated by François ARMAND almost 3 years ago

  • Target version changed from 6.2.8 to 6.1.14

OK, found the problem, thanks for reporting!

Actions #4

Updated by François ARMAND almost 3 years ago

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

Updated by François ARMAND almost 3 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/3659
Actions #6

Updated by François ARMAND almost 3 years ago

  • Status changed from Pending technical review to Pending release
Actions #7

Updated by Nicolas CHARLES over 2 years ago

  • Fix check changed from To do to Checked
Actions #8

Updated by Vincent MEMBRÉ over 2 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.14 and 6.2.8 which were released today.

Actions

Also available in: Atom PDF