Project

General

Profile

Actions

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 5 years ago. Updated almost 4 years ago.

Status:
Released
Priority:
2
Category:
Web - Maintenance
Target version:
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
Priority:
60

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.


Related issues

Related to Rudder - Bug #10664: Configuration file of Rudder mention that we may change "LDAP DIT configuration", which is wrongReleasedNicolas CHARLESActions
Actions #1

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 3.1.7 to 3.1.8
Actions #2

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 3.1.8 to 3.1.9
Actions #3

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 3.1.9 to 3.1.10
Actions #4

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.10 to 3.1.11
Actions #5

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.11 to 3.1.12
Actions #6

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions #8

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #9

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #10

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #11

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #12

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #13

Updated by Jonathan CLARKE about 4 years ago

  • 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
Actions #14

Updated by Benoît PECCATTE about 4 years ago

  • Priority set to 45
Actions #15

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #16

Updated by Benoît PECCATTE about 4 years ago

François: shouldn't we have a 404 page now in this case ?

Actions #17

Updated by François ARMAND about 4 years ago

  • 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.

Actions #18

Updated by François ARMAND about 4 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #19

Updated by François ARMAND about 4 years ago

  • 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
Actions #20

Updated by Nicolas CHARLES about 4 years ago

  • Related to Bug #10664: Configuration file of Rudder mention that we may change "LDAP DIT configuration", which is wrong added
Actions #21

Updated by François ARMAND about 4 years ago

  • Status changed from Pending technical review to Pending release
Actions #22

Updated by Vincent MEMBRÉ almost 4 years ago

  • 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.

Actions

Also available in: Atom PDF