Actions
Bug #16224
closed
Missing documentation on openssl incompatibilities between 4.x and 5.0
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
104
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
We had a problem because of a bug where openssl version prior to 1.0.1 were incompatible with version 1.0.2 and up. So when you migrate rudder from 4.X to 5.0, you can have agent <-> server connection failing.
The only solution in that cases are to update agent to a compatible openssl version (ie: use 5.0 agent with embeded ssl) or use relay server built with a specific openssl version compatible with both pre- and post-1.0.1 version.
This need to be documented in upgrade, with a big warning.
Updated by François ARMAND about 5 years ago
- Status changed from New to In progress
Updated by François ARMAND about 5 years ago
- Related to Bug #13690: Impossible to update promises when using a debian9 or Ubuntu 18 server and older distributions as Nodes (incompatible openssl version) added
Updated by François ARMAND about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-doc/pull/644
Updated by François ARMAND almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-doc|4d1a9039f6578c5328a857b3385b8580d3d38506.
Updated by Alexis Mousset almost 5 years ago
- Name check changed from To do to Reviewed
Updated by François ARMAND almost 5 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.15 which was released today.
Actions