Actions
Bug #25687
closedBug #25530: Group properties wrongly appear empty when group has no member nodes
Same as parent ticket for branch 8.1
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
142
Name check:
To do
Fix check:
Error - Fixed
Regression:
Yes
Description
In 8.1, when a group has no nodes, the properties appear empty
Updated by Nicolas CHARLES 2 months ago
- Priority changed from To review to 1 (highest)
Updated by Clark ANDRIANASOLO 2 months ago
- Has duplicate Bug #25154: Creating conflicting properties can break the server added
Updated by Clark ANDRIANASOLO 2 months ago
- Status changed from New to In progress
- Assignee set to Clark ANDRIANASOLO
Updated by Clark ANDRIANASOLO 2 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5953
Updated by Clark ANDRIANASOLO about 2 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|759e7a13caacfb6aeb93ff3cf0b65f492af107cf.
Updated by Alexis Mousset about 2 months ago
- Fix check changed from To do to Error - Blocking
Updated by Alexis Mousset about 2 months ago
- Fix check changed from Error - Blocking to Error - Fixed
Updated by Vincent MEMBRÉ about 2 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.8 and 8.2.1 which were released today.
Actions