Project

General

Profile

Actions
Copy link

Bug #6482

closed

Node API cannot get pending and refused node details

Added by Vincent MEMBRÉ over 9 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
François ARMAND
Category:
API
Target version:
3.0.4
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When using 'GET /api/latest/nodes/id' on an id of a pending or deleted node i get an error message telling that the node is not found

The semantic of this requests is to get the informations on a node, whatever the status is is in.

This was introduced when we canted to get the node properties in the node details, we introduced a dependency on the fact that the node was accepted.

We should better use a "NonAcceptedNode" object (with data correctly set) or put the NodeProperties directly (with an empty set)

The first solution would force us to treat the new data we add in a node, but it will add an object with a blurred meaning

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ over 9 years ago

  • Status changed from New to In progress
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/844
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 9 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.4 which was released today.

Actions
Copy link

Also available in: Atom PDF