Actions
Bug #3179
closedThe rule list doesn't complain when a rule refers to a non existing group
Status:
Released
Priority:
2
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Somehow, after a rollback, a Rule refered to a non existing Group.
The deployement failed, but there was no way to find on the rule grid if a rule is broken or not, and no way to repair without clicking everywhere or fixing in the LDAP..
Happens on rudder 2.5, but probably also on 2.4
Actions