Project

General

Profile

Actions

Bug #4018

closed

Reporting is never caught if the Rudder server UUID (/var/rudder/tmp/uuid.txt) was more than 33 characters long

Added by Nicolas CHARLES over 9 years ago. Updated about 9 years ago.

Status:
Released
Priority:
2
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

A typical uuid is around 37 characters, however the promises that generate the inventory wrongly truncate them to 33 :(
We have to raise this limit

Actions #1

Updated by Nicolas CHARLES over 9 years ago

  • Status changed from New to Pending technical review
  • Assignee set to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/209

I choose 50 as it is the length used at the top of the promise to check the uuid validity

Actions #2

Updated by Nicolas CHARLES over 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset policy-templates:commit:a7b2e564cfb339b86c0ddcefb84690e9e3b483fc.

Actions #3

Updated by Jonathan CLARKE over 9 years ago

Applied in changeset policy-templates:commit:d6ab436496acee5d8c5635ebe4fafd3eee1c8bcd.

Actions #4

Updated by Nicolas PERRON about 9 years ago

  • Subject changed from The inventory promises truncate the policy server uuid to 33 characters to Reporting is never caught if the Rudder server hostname was more than 33 characters long
Actions #5

Updated by Nicolas PERRON about 9 years ago

  • Subject changed from Reporting is never caught if the Rudder server hostname was more than 33 characters long to Reporting is never caught if the Rudder server UUID (/var/rudder/tmp/uuid.txt) was more than 33 characters long
Actions #6

Updated by Nicolas PERRON about 9 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.4.12 which was released today.
Check out:

Actions

Also available in: Atom PDF