Bug #22871
closed
Disable post-generation remote-run by default
Added by Alexis Mousset about 1 year ago.
Updated about 1 year ago.
Category:
Server components
Description
It was not working but should be fixed by #22870, but we don't want to enable this in a patch release. Let's disable it for now and enable it by default in 8.0.
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/4820
- Status changed from Pending technical review to In progress
I'm taking over this issue!
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request changed from https://github.com/Normation/rudder/pull/4820 to https://github.com/Normation/rudder/pull/4841
- Assignee changed from Vincent MEMBRÉ to Alexis Mousset
- Assignee changed from Alexis Mousset to Vincent MEMBRÉ
- Assignee changed from Vincent MEMBRÉ to Alexis Mousset
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
I have checked that the « Notify immediately nodes whose configuration changed » option is unchecked after a default 7.2 nightly server install, and that nodes which policies are updated are not immediately notified of this change.
However, checking the box to “yes” doens't seem to cause them to be notified either.
This bug's description says that this shoud have been fixed by #22870, but #22870 description looks at first sight unrelated to me.
So that's a “checked OK” for this one but the original bug seems to actually persist.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.8 and 7.3.3 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by