Project

General

Profile

Bug #14570

Build openssl for Slackware, so the agent can update promises

Added by Félix DALLIDET 4 months ago. Updated 3 months ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
126
Tags:

Description

Similar to #13690. On slackware 4-1-64 with an agent 5.0.9 and a debian9 server also in 5.0.9,

root@slackware-14-1-64:~# rudder agent run -ui                                                
Rudder agent 5.0.9.
Node uuid: 93e375c4-914e-49b0-98d2-c2aa3b3a6095
   error: Failed to establish TLS connection: (0 SSL_ERROR_SSL) tlsv1 alert decode error 
   error: No suitable server found
   error: Failed to establish TLS connection: (0 SSL_ERROR_SSL) tlsv1 alert decode error 
   error: No suitable server found
R: *********************************************************************************
* rudder-agent could not get an updated configuration from the policy server.   *
* This can be caused by:                                                        *
*   * an agent key that has been changed                                        *
*   * if this node is not accepted or deleted node on the Rudder root server    *
*   * if this node has changed policy server without sending a new inventory    *
* Any existing configuration policy will continue to be applied without change. *
*********************************************************************************
ok: Rudder agent promises were updated

and:

root@slackware-14-1-64:/opt/rudder# ldd /opt/rudder/bin/cf-agent | grep ssl
    libssl.so.1 => /lib/libssl.so.1 (0xb7445000)

The libssl used does not come with the agent and is too old to be compatible with the one of the server.


Related issues

Related to Rudder - Bug #13690: Impossible to update promises when using a debian9 or Ubuntu 18 server and older distributions as Nodes (incompatible openssl version)ReleasedActions

Associated revisions

Revision f51475bf (diff)
Added by Félix DALLIDET 4 months ago

Fixes #14570: Impossible to update promises when using a debian9 or Ubuntu 18 server and slackware

History

#1

Updated by Félix DALLIDET 4 months 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
#2

Updated by François ARMAND 4 months ago

  • Tags set to Sponsored
  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Priority changed from 0 to 126
#3

Updated by Félix DALLIDET 4 months ago

  • Status changed from New to In progress
  • Assignee set to Félix DALLIDET
#4

Updated by Félix DALLIDET 4 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Félix DALLIDET to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1841
#5

Updated by Félix DALLIDET 4 months ago

  • Status changed from Pending technical review to Pending release
#6

Updated by Vincent MEMBRÉ 3 months ago

  • Subject changed from Impossible to update promises when using a debian9 or Ubuntu 18 server and slackware to Slackware agent cannot update promises
#7

Updated by Vincent MEMBRÉ 3 months ago

  • Subject changed from Slackware agent cannot update promises to Build openssl for Slackware, so the agent can update promises
#8

Updated by Vincent MEMBRÉ 3 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.9 which was released today.

Also available in: Atom PDF