Bug #16825: When a node is in bootstrap mode there is no understandable way to unlock it from this state - Rudder - Issue Tracker

Actions

Copy link

Bug #16825

closed

When a node is in bootstrap mode there is no understandable way to unlock it from this state

Added by Félix DALLIDET almost 5 years ago. Updated about 4 years ago.

Status:

Released

Priority:

N/A

Assignee:

Benoît PECCATTE

Category:

Agent

Target version:

6.0.8

Pull Request:

https://github.com/Normation/rudder-a...

Severity:

Major - prevents use of part of Rudder | no simple workaround

UX impact:

User visibility:

Getting started - demo | first install | Technique editor and level 1 Techniques

Effort required:

Very Small

Priority:

Name check:

To do

Fix check:

Error - Fixed

Regression:

Description

It prompt the following messages:

[root@agent ~]# rudder agent update
   error: Failed to establish TLS connection: underlying network error ()
   error: No suitable server found
   error: Failed to establish TLS connection: underlying network error ()
   error: No suitable server found
R: Initial policies have been successfully downloaded from the policy server
error: Rudder agent promises could not be updated.

[root@agent ~]# rudder agent run
Rudder agent 6.0.3.release
Node uuid: 34d847ed-5888-4b96-92dc-ee179d93e9a7
   error: Failed to establish TLS connection: underlying network error ()
   error: No suitable server found
   error: Failed to establish TLS connection: underlying network error ()
   error: No suitable server found
error    Rudder agent was interrupted during execution by a fatal error
         Run with -i to see log messages.

## Summary #####################################################################
0 components verified in 1 directives
This summary is incomplete as the agent was interrupted during execution
Execution time: 0.04s
################################################################################

[root@agent ~]# rudder agent inventory
Agent is currently in bootstrap policies, cannot run an inventory, you need to download initial policies from the server

When in fact, we need to run rudder agent check

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Vincent MEMBRÉ almost 5 years ago

Target version changed from 6.0.4 to 6.0.5

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.0.5 to 6.0.6

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.0.6 to 6.0.7

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 6.0.7 to 6.0.8

Actions

Copy link

Updated by François ARMAND over 4 years ago

Severity set to Major - prevents use of part of Rudder | no simple workaround
User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required set to Very Small
Priority changed from 0 to 93

It seems that an easy step is to change message to tell "run rudder agent check"

Actions

Copy link

Updated by François ARMAND over 4 years ago

Assignee set to Nicolas CHARLES

Actions

Copy link

Updated by Nicolas CHARLES over 4 years ago

I ran rudder agent run, and got the following output

:/etc# rudder agent run
  notice: Trusting new key: MD5=0b1db1df33b21f477daa7a0e9af87f2f
R: Initial policies have been successfully downloaded from the policy server
ok: Rudder agent promises were updated.
Rudder agent 6.0.3-debian8
Node uuid: 361bc9fb-c9f6-46f9-a67d-956bc995fc54
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
   error: readjson: data error parsing JSON file '/var/rudder/cfengine-community/inputs/common/1.0/../../rudder-vars.json': No data
Start execution with config [0]

M| State         Technique                 Component                 Key                Message
E| repaired      Common                    ncf Initialization                           Configuration library initialization was repaired
E| repaired      Common                    Security parameters                          Some internal security parameters were adjusted
E| compliant     Common                    CRON Daemon                                  Cron daemon status was correct
E| repaired      Common                    Compute inventory splay   rudder_run_invent| Scheduling rudder_run_inventory was repaired
E| compliant     Inventory                 inventory                                    The inventory has been successfully sent

## Summary #####################################################################
5 components verified in 4 directives
   => 5 components in Enforce mode
      -> 2 compliant
      -> 3 repaired
Execution time: 2.46s
################################################################################

inventory was sent

Then rudder agent update is not that helpful

# rudder agent update
R: *********************************************************************************
* rudder-agent could not get an updated configuration from the policy server.   *
* This can be caused by:                                                        *
*   * 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. *
*********************************************************************************
error: Rudder agent promises could not be updated.

Actions

Copy link

Updated by Nicolas CHARLES over 4 years ago

starting with rudder agent update also succeed

rudder agent update
  notice: Trusting new key: MD5=0b1db1df33b21f477daa7a0e9af87f2f
R: Initial policies have been successfully downloaded from the policy server
ok: Rudder agent promises were updated.

Actions

Copy link