Bug #14431
closed
Accepted inventory without matching rudder node appears in quicksearch
Added by François ARMAND over 5 years ago.
Updated almost 5 years ago.
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Very Small
Description
If a an inventory is in accepted but there is no matching node in rudder branch, then the node can be seen in quickearch but when you click on the result, you get:
Node with id 78b15f0a-37cf-4f54-a91a-213d35d9673d was not found
Quicksearch results (for nodes) should not appear in that case: we must filter results by node present in nodeinfoservice.
- Assignee set to François ARMAND
- Target version changed from 4.1.21 to 4.1.22
- Target version changed from 4.1.22 to 4.1.23
- Priority changed from 50 to 49
- Target version changed from 4.1.23 to 4.1.24
- Target version changed from 4.1.24 to 588
- Priority changed from 49 to 48
- Target version changed from 588 to 5.0.13
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 48 to 47
- Target version changed from 5.0.14 to 5.0.15
- Priority changed from 47 to 46
- Status changed from New to In progress
- Priority changed from 46 to 45
- 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/2607
- Status changed from Pending technical review to Pending release
- Name check changed from To do to Reviewed
- Priority changed from 45 to 44
- Fix check changed from To do to Error - Blocking
- Fix check changed from Error - Blocking to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.15 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by