Some Salt Minions won't start after upgrading to 3006.13
search cancel

Some Salt Minions won't start after upgrading to 3006.13

book

Article ID: 404276

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • After Salt Minions were upgraded to 3006.13, some minions will not start. 
  • Minion logs (/var/log/salt/minion) show errors similar to this:
    [ERROR   ] An un-handled exception was caught by Salt's global exception handler:
    RuntimeError: OpenSSL 3.0's legacy provider failed to load. This is a fatal error by default, but cryptography supports running without legacy algorithms by setting the environment variable CRYPTOGRAPHY_OPENSSL_NO_LEGACY. If you did not expect this error, you have likely made a mistake with your OpenSSL configuration.
    salt-minion.service: Main process exited, code=exited, status=1/FAILURE
    salt-minion.service: Failed with result 'exit-code'.

Environment

Salt-Minion 3006.13

Cause

This can occur if no system openssl binary exists on the minion

Resolution

This has been resolved in 3006.14 which can be found here:
New Releases - Salt 3006.14  

3006.14 Release Notes  

Additional Information