Bug #12324
closed
Root server can be disable with node lifecycle "ignore" "set empty policies"
Added by Nicolas CHARLES about 6 years ago.
Updated almost 6 years ago.
Category:
Server components
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
- Target version changed from 4.3.0~rc2 to 4.3.0~rc3
- 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.
- Status changed from New to In progress
- Target version changed from 4.3.0~rc3 to 4.3.0
- 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
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.
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.0 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by