Project

General

Profile

Actions

Bug #11622

closed

"rudder agent update" always displays success message, even if update failed

Added by Florian Heigl over 6 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Agent
Target version:
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.

Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Bug #11048: Rudder agent update returns 0 even if update failsReleasedAlexis MoussetActions
Actions

Also available in: Atom PDF