Project

General

Profile

Actions

Bug #20996

closed

A node update in bootstrap/initial policies should not fail

Added by Félix DALLIDET about 2 years ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
First impressions of Rudder
Effort required:
Priority:
77
Name check:
To do
Fix check:
Checked
Regression:
No

Description

Several issues here that are really counter intuitive for the user.
When a node fails to run its first inventory in the postinst, it will stay in the bootstrap policies, which requires to run 'rudder agent update' to be run.
But then, if the node communicates with its policy server, send its first successful inventory, but we do not accept it, the command 'rudder agent update' will fail with the following:

root@agent1:~# rudder agent update
   error: Can't stat file '/var/rudder/share/f49b0730-d428-4289-a0f7-de18c2ce2235/rules/cfengine-community/rudder-promises-generated' on '192.168.25.4' in files.copy_from promise, it may be missing or access may not be authorized
   error: Errors encountered when actuating files promise '/var/rudder/cfengine-community/inputs/rudder-promises-generated.tmp'
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 policies could not be updated.

This behavior is pretty misleading as the same command gives different expected results depending on how far we are in the accepting process. I feel like we should have a dedicated command for the specific bootstrap update which should be repeatable.


Subtasks 1 (0 open1 closed)

Bug #22623: change update message for node in initial policiesReleasedAlexis MoussetActions
Actions #1

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.0.3 to 7.0.4
Actions #2

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.0.4 to 7.0.5
  • Priority changed from 80 to 79
Actions #3

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 7.0.5 to 7.0.6
  • Priority changed from 79 to 78
Actions #4

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 7.0.6 to 7.0.7
  • Priority changed from 78 to 0
Actions #5

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 7.0.7 to 7.0.8
Actions #6

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 7.0.8 to 1002
Actions #7

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 1002 to 7.1.7
Actions #8

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.1.7 to 7.1.8
Actions #9

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.1.8 to 7.1.9
Actions #10

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.1.9 to 7.1.10
Actions #11

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.1.10 to 1016
Actions #12

Updated by Alexis Mousset over 1 year ago

  • Target version changed from 1016 to 7.2.5
Actions #13

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.2.5 to 7.2.6
Actions #14

Updated by Benoît PECCATTE about 1 year ago

  • UX impact set to It bothers me each time
  • Priority changed from 0 to 77
  • Regression set to No
Actions #15

Updated by Benoît PECCATTE about 1 year ago

I suggest we just check if we are still in initial policies and then just give proper message to the user "Agent not yet accepted on the server"

Actions #16

Updated by Benoît PECCATTE about 1 year ago

  • Status changed from New to In progress
  • Assignee set to Benoît PECCATTE
Actions #17

Updated by Benoît PECCATTE about 1 year ago

  • Subtask #22623 added
Actions #18

Updated by Benoît PECCATTE about 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1812
Actions #19

Updated by Benoît PECCATTE about 1 year ago

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

Updated by Alexis Mousset about 1 year ago

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

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.2.6 and 7.3.1 which were released today.

Actions

Also available in: Atom PDF