Project

General

Profile

Bug #8458

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

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

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Severity:
User visibility:
Effort required:
Priority:

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

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

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

Updated by Nicolas CHARLES over 4 years ago

#2

Updated by Nicolas CHARLES over 4 years ago

  • Status changed from New to In progress
#3

Updated by Nicolas CHARLES over 4 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/967
#4

Updated by Nicolas CHARLES over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.12 to 3.1.11
#6

Updated by Vincent MEMBRÉ over 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.11 and 3.2.4 which were released today.

Also available in: Atom PDF