Actions
Bug #19146
closed
Bug #19138: Add an option to invert result of a node query
Bug #19143: inverting a request with 0 answer leads to 0 answer
in some case inverting a request leads to an error and 0 results
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
In parent ticket, we tried to correct the fact that node search "invert" leads to 0 results when the sub query returns 0 results.
In some cases (depending on filters I believe), we had an error at some point, which was not diplayed in UI, and lead to 0 results.
Updated by François ARMAND over 3 years ago
- Status changed from New to In progress
Updated by François ARMAND over 3 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/3586
Updated by François ARMAND over 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|f3e3a9095b865599802269667023ad2900b88c9f.
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.2.6 to 6.2.5
Updated by Vincent MEMBRÉ over 3 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.2.5 which was released today.
Actions