Project

General

Profile

Actions
Copy link

Bug #8458

closed

If using Rudder Server 3.1 and a node with agent 3.2, protocol used is TLS

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

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
System techniques
Target version:
3.1.11
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

If the node has Rudder 3.2 but the server is 3.1, promises don't force protocol version, so it default to TLS
So in this case, reverse lookup is made, independently from the configuration in the webapp, and it break the communication

Subtasks 2 (0 open — 2 closed)

User story #8459: Document precisely compatibility between servers and nodes in 3.2 docReleasedJonathan CLARKE2016-06-03Actions
Bug #8461: Merge issue after 8458 in 3.2ReleasedBenoît PECCATTE2016-06-03Actions

Related issues 1 (0 open — 1 closed)

Related to Rudder - User story #7690: Force classic protocol on CFEngine 3.7ReleasedNicolas CHARLES2015-12-24Actions
Actions
Copy link

Also available in: Atom PDF