Bug #3737
closed
"Rules to be applied" in pending nodes doesn't find Rules on system groups
Added by Jonathan CLARKE about 11 years ago.
Updated about 11 years ago.
Category:
Web - Nodes & inventories
Description
If I create a Rule on the system group "All nodes", and then I go to the "Accept new nodes" screen, and click on the "magnifying glass" icon, I expect to see that Rule there. However, it is not there.
I checked, and this feature works fine for the same node, with a Rule that is applied to a "manually created" group, with criteria "Node ID is defined" (basically the same group as "All nodes"). I suspect therefore that this is a limitation due to system groups.
This happens in 2.6 and 2.7 currently, but does not apply to 2.4 or 2.5.
- Assignee set to François ARMAND
- Assignee changed from François ARMAND to Vincent MEMBRÉ
Vincent, can you look into this when you're back from vacation, since François is on vacation now? (damn the summer... :p)
- Target version changed from 2.6.3 to 2.6.4
Jonathan CLARKE wrote:
Vincent, can you look into this when you're back from vacation, since François is on vacation now? (damn the summer... :p)
Vincent, can you please work on this this week? This should be fixed pretty swiftly, it can be very misleading (accepting a node thinking no configs will apply... but actually they do).
- Status changed from 8 to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/293
- Status changed from Pending technical review to In progress
- Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
- % Done changed from 0 to 90
Vincent, I made some remarks on the pull request; could you adress them ?
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
I addressed your returns, Nicolas!
- Status changed from Pending technical review to Pending release
- % Done changed from 90 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.4, which was released today.
Check out:
Also available in: Atom
PDF