Actions
Bug #11622
closed"rudder agent update" always displays success message, even if update failed
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
50
Name check:
Fix check:
Regression:
Description
If a node is able to access the system policy but not it's own:
It's still saying, at the same time, that the update failed and that they were updated.
This has been wrong since the rudder wrapper got added.
# rudder agent update R: ********************************************************************************* * rudder-agent could not get an updated configuration from the policy server. * * This can be caused by: * * * an incorrect DNS resolution of this node * * * an agent key that has been changed * * * if this node is not accepted or deleted node on the Rudder root server * * * if this node has changed policy server without sending a new inventory * * Any existing configuration policy will continue to be applied without change. * ********************************************************************************* ok: Rudder agent promises were updated.
Updated by Alexis Mousset about 7 years ago
- Subject changed from Please fix rudder agent messages to "rudder agent update" always displays success message, even if update failed
- Target version set to 4.1.8
Linked to #11048, IIRC it is a change in the agent behavior between 3.1 and 4.1 that caused the return code (and user message) issue.
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.8 to 4.1.9
Updated by Benoît PECCATTE about 7 years ago
- Is duplicate of Bug #11048: Rudder agent update returns 0 even if update fails added
Updated by Benoît PECCATTE about 7 years ago
- Status changed from New to Rejected
Actions