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.
Category:
System integration
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
It would appear that rudder-init adds an extra space for each additional trusted network registered:
(better with the picture)
- 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
- 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
- Priority changed from 1 (highest) to 2
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset packages:commit:8fd2feb1c62e786e7b98fd79ab35216bb1edf1e2.
Applied in changeset packages:commit:8cf286e907cc0c30ceedc15fd8fd72c1f1d3614b.
- 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
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.17, which was released today.
Check out:
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Jonathan CLARKE 
Updated by Nicolas PERRON 