Bug #22170
closed
A new group display no nodes while all linux are selected
Description
Hello guys !
I just encounters a massive thing that make me hate both myself AND Rudder.
I create a rule wich deploy PHP / FPM/ etc... This works really fine, and to use it I must create a group and add it to the rule.
And by default when you create a group the criteria take all the node, which happened and I end up with php deploy on half on my infrastructure.
I think it's extremely dangerous when you industrialize massively your Architecture. User is responsible of what he's doing but Rudder should have safe guard.
The idea behind this issue, is to when you create a new group by default no node is add to the group.
best regards,
Alexis TARUSSIO
Files
| clipboard-202401251753-6cail.png (89.7 KB) clipboard-202401251753-6cail.png | |||
| clipboard-202401251757-06mh2.png (21.6 KB) clipboard-202401251757-06mh2.png |
Updated by Alexis Mousset about 3 years ago
- Category set to Web - UI & UX
- Target version set to 7.3.0~beta1
- UX impact set to I hate Rudder for that
- User visibility set to Infrequent - complex configurations | third party integrations
- Effort required set to Very Small
This makes a lot of sense.
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 7.3.0~beta1 to 7.3.0~rc1
Updated by Elaad FURREEDAN almost 3 years ago
In fact, we cannot have empty criteria from the UI
Updated by Elaad FURREEDAN almost 3 years ago
- Related to Bug #22400: Empty group criteria breaks UI for adding new criteria added
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.3.0~rc1 to 7.3.0
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.3.0 to 7.3.1
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.3.1 to 7.3.2
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.3.2 to 7.3.3
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.3.3 to 7.3.4
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.3.4 to 7.3.5
Updated by Alexis Mousset over 2 years ago
- Target version changed from 7.3.5 to 7.3.6
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.3.6 to 7.3.7
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.3.7 to 7.3.8
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.3.8 to 7.3.9
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.3.9 to 7.3.10
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.3.10 to 7.3.11
Updated by François ARMAND almost 2 years ago
We don't have a simple way to change that apport from changing the default selector for the newly created group.
We could use something like a never validating regex, but I'm not sure it woon't be more surprising.
Updated by François ARMAND almost 2 years ago
- Target version changed from 7.3.11 to 8.1.0~alpha1
We should wait for a major release to change that default behavior.
Updated by François ARMAND almost 2 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND almost 2 years ago
- Status changed from In progress to New
- Assignee deleted (
François ARMAND) - Target version changed from 8.1.0~alpha1 to 7.3.11
OK, actually the main problem is that the group is displayed empty at creation until we click on "search" while it is not. So in the first dyn group update, it changes, which is extremely surprising.
Updated by François ARMAND almost 2 years ago
- Tracker changed from Enhancement to Bug
- Subject changed from Group Criteria to null not to all node to A new group display no nodes while all linux are selected
- Priority set to 0
Updated by François ARMAND almost 2 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND almost 2 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/5255
Updated by Anonymous almost 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|0e1b18a8c9bd9a4774813c26c36a416b6a50d8aa.
Updated by François ARMAND almost 2 years ago
- File clipboard-202401251753-6cail.png clipboard-202401251753-6cail.png added
- File clipboard-202401251757-06mh2.png clipboard-202401251757-06mh2.png added
- Fix check changed from To do to Checked
It now correctly handled:
- when created, the group is saved with an empty selector: 
- we really don't have any node for that group: 
And then, we can go to group criteria, hit search then save directly to get all linux nodes like before, or actually specify criteria.
Updated by Vincent MEMBRÉ almost 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.11 which was released today.
Updated by François ARMAND about 1 year ago
- Related to Bug #25820: On new groups, adding a prop leads to "No query defined for group" error added
Updated by François ARMAND about 1 year ago
- Related to Bug #25026: Groups can be created without any research criteria added