Project

General

Profile

Actions

Bug #25967

open

Documention should advice to trigger agent run after promote a node to relay

Added by Elaad FURREEDAN 16 days ago. Updated 14 days ago.

Status:
Pending release
Priority:
N/A
Category:
Documentation
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

When we promote a node to relay and put a node immediately by following the doc, we got an error on the node:

root@cs81_ubuntu24:~# rudder agent server-keys-reset
Resetting all known keys allows the node to connect to another server than the one it is currently trusting.
Do yo really want to do it?
Type ctrl-c to abort now or enter to continue

   error: Failed to establish TLS connection: underlying network error (Connection reset by peer)
   error: No suitable server found for '/var/rudder/cfengine-community/inputs'
   error: Promise belongs to bundle 'update' in file '/var/rudder/cfengine-community/inputs/failsafe.cf' near line 104
   error: Errors encountered when actuating files promise '/var/rudder/cfengine-community/inputs'
   error: Failed to establish TLS connection: underlying network error ()
   error: No suitable server found for '/var/rudder/ncf/common'
   error: Promise belongs to bundle 'update' in file '/var/rudder/cfengine-community/inputs/failsafe.cf' near line 112
   error: Errors encountered when actuating files promise '/var/rudder/ncf/common'
R: ******************************************************************************
* rudder-agent could not get an updated configuration from the policy server.   *
* This can be caused by:                                                        *
*   * a networking issue                                                        *
*   * an unavailable server                                                     *
*   * if the node's IP is not in the allowed networks of its policy server.     *
*********************************************************************************
error: Rudder agent policies could not be updated.
ok: Rudder agent state has been reset.
root@cs81_ubuntu24:~# rudder agent update
  notice: Trusting new key: MD5=a99af06b1ca8773f12b92fc666608ab4
R: Initial policies have been successfully downloaded from the policy server
ok: Rudder agent policies were updated.

It because the relay didn't download the initial policies, we should run the agent. But the documentation doesn't mention it.


Subtasks 1 (1 open0 closed)

Scale-out relay - Bug #25968: Add a tip message after promote a node to relay to trigger agent runPending releaseAlexis MoussetActions
Actions #1

Updated by Elaad FURREEDAN 16 days ago

  • Status changed from New to In progress
Actions #2

Updated by Elaad FURREEDAN 16 days ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Elaad FURREEDAN to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-doc/pull/1075
Actions #3

Updated by Elaad FURREEDAN 16 days ago

  • Subtask #25968 added
Actions #4

Updated by Anonymous 15 days ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by Alexis Mousset 15 days ago

  • Fix check changed from To do to Checked
Actions #6

Updated by Vincent MEMBRÉ 14 days ago

This bug has been fixed in Rudder 8.1.9 and 8.2.2 which were released today.

Actions

Also available in: Atom PDF