Project

General

Profile

Actions

Bug #9234

closed

Bug #8818: rudder_promises_generated is now called rudder-promises-generated

When upgrading from 3.2 to 4.0, nodes cannot get their promises

Added by Nicolas CHARLES almost 8 years ago. Updated over 7 years ago.

Status:
Released
Priority:
1
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When upgrading from 3.2 to 4.0, nodes cannot get their promises, because they are looking for file rudder_promises_generated on the server, rather than the rudder-promises-generated that is generated
Error is:

rudder  verbose: 192.168.41.4> A public key was already known from agent3.rudder.local/192.168.41.4 - no trust required
rudder  verbose: 192.168.41.4> The public key identity was confirmed as root@agent3.rudder.local
rudder  verbose: 192.168.41.4> Authentication of client agent3.rudder.local/192.168.41.4 achieved
rudder     info: 192.168.41.4> Couldn't resolve (realpath: No such file or directory) filename: /var/rudder/share/d48a5baa-3c30-4ad3-a5f3-34510cdcde7c/rules/cfengine-community/rudder_promises_generated
rudder     info: 192.168.41.4> Access control in sync
rudder  verbose: 192.168.41.4> REFUSAL to (user=root,ip=192.168.41.4) of request: SYNCH 1475670890 STAT /var/rudder/share/d48a5baa-3c30-4ad3-a5f3-34510cdcde7c/rules/cfengine-community/rudder_promises_generated
rudder  verbose: 192.168.41.4> Filename /usr/share/ncf/tree/ncf_hash_file is resolved to /usr/share/ncf/tree/ncf_hash_file

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #10049: A 4.1 agent cannot fetch its promises from a 3.1 serverReleasedBenoît PECCATTEActions
Actions #1

Updated by Nicolas CHARLES almost 8 years ago

  • Related to Bug #8818: rudder_promises_generated is now called rudder-promises-generated added
Actions #2

Updated by Nicolas CHARLES almost 8 years ago

  • Translation missing: en.field_tag_list set to Blocking 4.0
Actions #3

Updated by Nicolas CHARLES almost 8 years ago

Solution is to generate both files, so that in the future, we'll be able to drop the old one

Actions #4

Updated by Nicolas CHARLES almost 8 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions #5

Updated by Nicolas CHARLES almost 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1050
Actions #6

Updated by Nicolas CHARLES almost 8 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #7

Updated by Benoît PECCATTE almost 8 years ago

  • Target version changed from 4.0.0~rc2 to 318
Actions #8

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 318 to 4.0.0~rc2
Actions #9

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.0~rc2 to 4.0.0~rc1
Actions #10

Updated by Vincent MEMBRÉ over 7 years ago

  • Related to deleted (Bug #8818: rudder_promises_generated is now called rudder-promises-generated)
Actions #11

Updated by Vincent MEMBRÉ over 7 years ago

  • Parent task set to #8818
Actions #12

Updated by Alexis Mousset over 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.

Actions #13

Updated by Nicolas CHARLES over 7 years ago

  • Related to Bug #10049: A 4.1 agent cannot fetch its promises from a 3.1 server added
Actions

Also available in: Atom PDF