Bug #10049: A 4.1 agent cannot fetch its promises from a 3.1 server - Rudder - Issue Tracker

Actions

Copy link

Bug #10049

closed

A 4.1 agent cannot fetch its promises from a 3.1 server

Added by Nicolas CHARLES about 7 years ago. Updated about 7 years ago.

Status:

Released

Priority:

N/A

Assignee:

Benoît PECCATTE

Category:

System techniques

Target version:

4.0.4

Pull Request:

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

Severity:

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

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

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 1 (0 open — 1 closed)

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas CHARLES about 7 years ago

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

Actions

Copy link

Updated by Vincent MEMBRÉ about 7 years ago

Target version changed from 3.1.18 to 3.1.19

Actions

Copy link

Updated by Jonathan CLARKE about 7 years 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

Actions

Copy link

Updated by Jonathan CLARKE about 7 years 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

Actions

Copy link

Updated by Alexis Mousset about 7 years ago

Target version changed from 4.1.0 to 4.0.4

Also exists in 4.0.

Actions

Copy link

Updated by Alexis Mousset about 7 years ago

Status changed from New to In progress
Assignee set to Alexis Mousset

Actions

Copy link

Updated by Alexis Mousset about 7 years 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

PR https://github.com/Normation/rudder-techniques/pull/1126

Actions

Copy link

Updated by Alexis Mousset about 7 years 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

Actions

Copy link