Actions
User story #17666
closedNode status API must not return an error when the node is not here
Pull Request:
UX impact:
Suggestion strength:
Want - This would make my life a lot easier but I can manage without
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Name check:
To do
Fix check:
Checked
Regression:
Description
We don't have a good way to get a node status. If we ask for node information, we get an error:
And lots of errors if we need to wait for node to appears, like in RTF when a node is created:
while ! curl --insecure --silent --header \"X-API-Token: \$(cat /var/rudder/run/api-token)\" https://localhost/rudder//api/latest/nodes/959531df-4401-4092-8202-b8d1d5276157 | grep -q success; do sleep 1; done; curl --insecure --silent --header \"X-API-Token: \$(cat /var/rudder/run/api-token)\" --request POST https://localhost/rudder//api/latest/nodes/pending/959531df-4401-4092-8202-b8d1d5276157 --data \"status=accepted\"'" -- {"action":"changePendingNodeStatus","result":"success","data":{"nodes":[{"id":"959531df-4401-4092-8202-b8d1d5276157","status":"accepted","hostname":"agent3.rudder.local","osName":"Centos","osVersion":"[6.10]","machineType":"Virtual"}]}}Connection to 127.0.0.1 closed.
We need a "nodes/uuid/status" API that returns just node status, and "missing" is an expected result for it.
Files
Updated by François ARMAND over 4 years ago
- Tracker changed from Bug to User story
- Subject changed from Node status API must not return an error when the node is node here to Node status API must not return an error when the node is not here
- Target version changed from 5.0.18 to 6.1.2
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority deleted (
0) - Suggestion strength set to Want - This would make my life a lot easier but I can manage without
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.2 to 6.1.3
Updated by François ARMAND over 4 years ago
- Target version changed from 6.1.3 to 6.1.4
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.4 to 6.1.5
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.5 to 6.1.6
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.6 to 6.1.7
Updated by François ARMAND about 4 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 4 years ago
- Target version changed from 6.1.7 to 6.2.0~beta1
Updated by François ARMAND about 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Elaad FURREEDAN
- Pull Request set to https://github.com/Normation/rudder/pull/3300
Updated by François ARMAND about 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|3b0f48b5c9c2269f128c2b512cf1182e1e55077c.
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.2.0~beta1 which was released today.
Updated by François ARMAND about 4 years ago
- Related to User story #18483: Documentation for /nodes/status page added
Updated by François ARMAND about 4 years ago
- Fix check changed from To do to Checked
Actions