Project

General

Profile

Bug #10049

A 4.1 agent cannot fetch its promises from a 3.1 server

Added by Nicolas CHARLES 10 months ago. Updated 7 months ago.

Status:
Released
Priority:
N/A
Category:
Initial promises & sys tech
Target version:
Target version (plugin):
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Effort required:
Priority:
0

Description

When installing a 4.1 agent, it cannot fetch its promises from the 3.1 server, as it looks for rudder-promises-generated file, while rudder_promises_generated is the generated file in 3.1

2017-01-23T10:27:16+0000  verbose: 192.168.41.6>      Received:    STAT /var/rudder/share/5ee1fcf2-54b4-4f7a-bba2-dca5166abe00/rules/cfengine-community/rudder-promises-generated
2017-01-23T10:27:16+0000     info: 192.168.41.6> Failed to canonicalise filename '/var/rudder/share/5ee1fcf2-54b4-4f7a-bba2-dca5166abe00/rules/cfengine-community/rudder-promises-generated' (realpath: No such file or directory)
2017-01-23T10:27:16+0000  verbose: 192.168.41.6> REFUSAL to (user=root,ip=192.168.41.6) of request: SYNCH 1485167236 STAT /var/rudder/share/5ee1fcf2-54b4-4f7a-bba2-dca5166abe00/rules/cfengine-community/rudder-promises-generated
<pre>

Copying the file with - solves the issue

Subtasks

Bug #10391: Generate rudder-promises-generated on 3.1 serversReleasedBenoît PECCATTE


Related issues

Related to Rudder - Bug #9234: When upgrading from 3.2 to 4.0, nodes cannot get their promises Released 2016-10-05

Associated revisions

Revision aa00bbe2
Added by Alexis MOUSSET 8 months ago

Fixes #10049: A 4.1 agent cannot fetch its promises from a 3.1 server

History

#1 Updated by Nicolas CHARLES 10 months ago

  • Related to Bug #9234: When upgrading from 3.2 to 4.0, nodes cannot get their promises added

#2 Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 3.1.18 to 3.1.19

#3 Updated by Jonathan CLARKE 8 months ago

  • Target version changed from 3.1.19 to 4.1.0
  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security

#4 Updated by Jonathan CLARKE 8 months ago

  • Severity changed from Critical - prevents main use of Rudder | no workaround | data loss | security to Major - prevents use of part of Rudder | no simple workaround

#5 Updated by Alexis MOUSSET 8 months ago

  • Target version changed from 4.1.0 to 4.0.4

Also exists in 4.0.

#6 Updated by Alexis MOUSSET 8 months ago

  • Status changed from New to In progress
  • Assignee set to Alexis MOUSSET

#7 Updated by Alexis MOUSSET 8 months ago

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

#8 Updated by Alexis MOUSSET 8 months ago

A little explanation here. While merging initial promises into techniques 4.0, we renamed rudder_promises_generated to rudder-promises-generated (#7927). Just after, we added generation of the old rudder_promises_generated back (#9234), before releasing 4.0.0.

This means that:

  • All released Rudder server generate the rudder_promises_generated file
  • 3.1 agents read the rudder_promises_generated file
  • 4.0/4.1 agents read the rudder-promises-generated

It breaks compatibility between 4.0/4.1 nodes and 3.1 servers (only when upgrading the agents).

This fix will be:

  • Make 4.0/4.1 agents use the rudder_promises_generated file
  • To allow compatibility of released 4.0 nodes (4.0.0 to 4.0.3) with 3.1, will add the generation of rudder-promises-generated to 3.1 servers too

#9 Updated by Alexis MOUSSET 8 months ago

  • Status changed from Pending technical review to Pending release

#10 Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from Pending release to Released
  • Priority set to 0

This bug has been fixed in Rudder 4.0.4 and 4.1.1 which were released today.

Also available in: Atom PDF