[4.2] Patch - Feb 3, 2022

This document provides an overview of resolved issues and other improvements in the Fortanix Data Security Manager (DSM) 4.2 Patch (4.2.1533) release.

WARNING
  • It is “REQUIRED” to upgrade Fortanix DSM to version 4.1 before upgrading to version 4.2 Patch (4.2.1533).
NOTE
  • After the software package is uploaded, the expected time to upgrade a 3-node cluster is about 1 hour.

1. Bug Fixes

  • Git protocol for plugin registry is moved to HTTPS. (JIRA: PROD-4052)
  • Fixed panic caused by Stats API due to incorrect input parameter. (JIRA: PROD-4008)
  • Fixed Azure BYOK scan API error. (JIRA: PROD-3967)
  • Fixed an issue where excessive audit log was causing Cassandra to be unstable with a high CPU load average. (JIRA: PROD-3961)
  • Fixed an issue where AWS sync keys operation returned 100 keys due to the pagination issue. (JIRA: PROD-3840)
  • Fixed AWS scan error. (JIRA: PROD-3787)

2. Improvements

  • Enforced a limit on what GET logs return. (JIRA: PROD-3632)
  • Added mechanism to remove/cleanup Elasticsearch completely (including backup job update). (JIRA: PROD-3174)

3. Known Issues

  • Azure BYOK plugin returns out of memory error in case the key vault has more than a certain number of keys (JIRA: PROD-3568).
  • exclude is not working in the proxy config for operations such as attestation (JIRA: PROD-3311).
  • Single node updates can have kube-dns pending POD (JIRA: DEVOPS-1683).

4. Installation

To download the DSM SGX (on-prem/Azure) and Software (AWS/Azure/VMWare) packages, click here.

Comments

Please sign in to leave a comment.

Was this article helpful?
0 out of 0 found this helpful