Bug #8017
closed
Adding an authorized network when "common-root" directive is missing seems to work, but actually fails
Added by François ARMAND about 8 years ago.
Updated almost 7 years ago.
Category:
Web - Maintenance
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Description
When "common-root" directive is missing, for example because rudder-init was not done correctly, you can still go to the admin page in Rudder and add authorized networks. Saving seems to work (perhaps due to #7144).
At least seen in 3.1, perhaps happening before.
- Target version changed from 3.1.7 to 3.1.8
- Target version changed from 3.1.8 to 3.1.9
- Target version changed from 3.1.9 to 3.1.10
- Target version changed from 3.1.10 to 3.1.11
- Target version changed from 3.1.11 to 3.1.12
- Target version changed from 3.1.12 to 3.1.13
- Target version changed from 3.1.13 to 3.1.14
- Target version changed from 3.1.14 to 3.1.15
- Target version changed from 3.1.15 to 3.1.16
- Target version changed from 3.1.16 to 3.1.17
- Target version changed from 3.1.17 to 3.1.18
- Target version changed from 3.1.18 to 3.1.19
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Target version changed from 3.1.19 to 3.1.20
François: shouldn't we have a 404 page now in this case ?
- Effort required set to Very Small
- Priority changed from 45 to 60
That entry is not checked for, but you are right: we should be more precise about what is checked regarding the run of rudder-init, and will add it.
- Status changed from New to In progress
- Assignee set to François ARMAND
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/1649
- Related to Bug #10664: Configuration file of Rudder mention that we may change "LDAP DIT configuration", which is wrong added
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.20, 4.0.5 and 4.1.2 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by