Project

General

Profile

Actions

Bug #12324

closed

Root server can be disable with node lifecycle "ignore" "set empty policies"

Added by Nicolas CHARLES almost 6 years ago. Updated almost 6 years ago.

Status:
Released
Priority:
N/A
Category:
Server components
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

We can disable the policies for Rudder Root server - so no new policies will be set, and so new nodes cannot fetch their policies
We ought to have some kind on limits on what state can be put on the Root Server

Actions #1

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.3.0~rc2 to 4.3.0~rc3
Actions #2

Updated by François ARMAND almost 6 years ago

  • Translation missing: en.field_tag_list set to Blocking 4.3
  • Subject changed from We can ignore or set empty policies for Rudder Root server, which is probably not what we want to Root server can be disable with node lifecycle "ignore" "set empty policies"
  • Assignee set to François ARMAND

In fact, we should not be able to change root server lifecycle at all.

Actions #3

Updated by François ARMAND almost 6 years ago

  • Status changed from New to In progress
Actions #4

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.3.0~rc3 to 4.3.0
Actions #5

Updated by François ARMAND almost 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1894
Actions #6

Updated by François ARMAND almost 6 years ago

I think we should keep the possibility to change lifecycle for other policy servers or rudder component.
At least, for realy servers, we must have it. We want to be able to keep only system policy on a relay (to make it works as a relay even if a user rule is not correct), or disable it, or whatever.
For Rudder component, it is less clear, but I don't see real problem on keeping it.

Actions #7

Updated by Rudder Quality Assistant almost 6 years ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND
Actions #8

Updated by François ARMAND almost 6 years ago

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

Updated by Alexis Mousset almost 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.3.0 which was released today.

Actions

Also available in: Atom PDF