Project

General

Profile

Actions

Bug #2169

closed

Accept new nodes history show short version of OS

Added by Jonathan CLARKE over 12 years ago. Updated about 12 years ago.

Status:
Released
Priority:
3
Category:
Web - Nodes & inventories
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

This (for example "Debian) is inconsistent with other displays that show the full version (ie "Debian GNU/Linux 6.0.2 (squeeze)")

Actions #1

Updated by Jonathan CLARKE about 12 years ago

  • Target version changed from 2.3.6 to 2.4.0~alpha4
Actions #2

Updated by François ARMAND about 12 years ago

  • Assignee set to Arthur ANGLADE
Actions #3

Updated by Arthur ANGLADE about 12 years ago

  • Status changed from 2 to In progress
Actions #4

Updated by François ARMAND about 12 years ago

  • Target version changed from 2.4.0~alpha4 to 2.4.0~alpha5
Actions #5

Updated by Arthur ANGLADE about 12 years ago

The field seems to be empty in current version. When looking on demo.rudder-project.org/rudder/secure/assetManager/manageNewServer the full OS version is correctly displayed, but not in history.

The variable used : "osFullName" is supposed to receive a long description about the os (distribution, type, version, etc)from LDAP in Srv.scala, and does not.

Actions #6

Updated by François ARMAND about 12 years ago

  • Status changed from In progress to Discussion
  • Assignee deleted (Arthur ANGLADE)
  • Target version changed from 2.4.0~alpha5 to 2.4.0~alpha6

OK, that bug should be looked by FAR or NCH, as it seems to be a deep problem.

Actions #7

Updated by Jonathan CLARKE about 12 years ago

  • Target version changed from 2.4.0~alpha6 to 2.4.0~alpha7
Actions #8

Updated by Nicolas CHARLES about 12 years ago

  • Status changed from Discussion to Pending technical review
  • Assignee set to Nicolas CHARLES

when we accept/refuse a node, and event is created in the eventlog, and the details within the event log are used to show the history
However, the serialisation of the osName was not valid (it wasn't the full os name).

Actions #9

Updated by Jonathan CLARKE about 12 years ago

Is this not a bug in 2.3 also?

Actions #10

Updated by Nicolas CHARLES about 12 years ago

indeed it is, i'm correcting also on 2.3

Actions #11

Updated by Nicolas CHARLES about 12 years ago

  • % Done changed from 0 to 100
Actions #12

Updated by Jonathan CLARKE about 12 years ago

  • Target version changed from 2.4.0~alpha7 to 2.3.7
Actions #13

Updated by François ARMAND about 12 years ago

  • Status changed from Pending technical review to Released

OK !

Actions

Also available in: Atom PDF