Actions
Bug #8458
closed
If using Rudder Server 3.1 and a node with agent 3.2, protocol used is TLS
Pull Request:
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
Updated by Nicolas CHARLES almost 8 years ago
- Related to User story #7690: Force classic protocol on CFEngine 3.7 added
Updated by Nicolas CHARLES almost 8 years ago
- Status changed from New to In progress
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/967
Updated by Nicolas CHARLES almost 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-techniques|8c60f41e72761c792097e571e633fc58fb073788.
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.12 to 3.1.11
Updated by Vincent MEMBRÉ almost 8 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.
- 3.1: Announce Changelog
- 3.2: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions