Project

General

Profile

Actions
Copy link

Bug #5103

closed

Authorized network sometimes have invalid values after rudder-init if you add more than one network

Added by Nicolas CHARLES over 10 years ago. Updated over 10 years ago.

Status:
Released
Priority:
2
Assignee:
Jonathan CLARKE
Category:
System integration
Target version:
2.6.17
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On unknown occasions, authorized networks contain space in them, and the promises generated contains this space which prevent nodes from fetching promises

There are regexps and tests preventing this, but somehow it can slip through (we never could reproduce this though ...)

One user got it on 2.10, but it could be on any version

Files

extra_whitespace2.png (10.8 KB) extra_whitespace2.png picture of the ui Lionel Le Folgoc, 2014-07-01 15:54
Actions
Copy link
 #1

Updated by Lionel Le Folgoc over 10 years ago

It would appear that rudder-init adds an extra space for each additional trusted network registered:

Actions
Copy link
 #2

Updated by Lionel Le Folgoc over 10 years ago

(better with the picture)

Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 10 years ago

  • Assignee set to Vincent MEMBRÉ
  • Priority changed from N/A to 1 (highest)
  • Target version set to 2.6.17

Yes, your are absolutely right Lionel.

The bug comes from rudder-init setting a wrong value in LDAP for allowed networks after the first one by putting a space before the value ...

Correcting it in 2.6

Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 10 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/427
Actions
Copy link
 #5

Updated by Jonathan CLARKE over 10 years ago

  • Priority changed from 1 (highest) to 2
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 10 years ago

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

Applied in changeset packages:commit:8fd2feb1c62e786e7b98fd79ab35216bb1edf1e2.

Actions
Copy link
 #7

Updated by Jonathan CLARKE over 10 years ago

Applied in changeset packages:commit:8cf286e907cc0c30ceedc15fd8fd72c1f1d3614b.

Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 10 years ago

  • Subject changed from Authorized network sometimes have invalid values, and prevent nodes from fetching promises to Authorized network sometimes have invalid values after rudder-init if you add more than one network
  • Category changed from Web - Config management to System integration
Actions
Copy link
 #9

Updated by Nicolas PERRON over 10 years ago

  • Status changed from Pending release to Released

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

Actions
Copy link

Also available in: Atom PDF