See below for the known issues common to all PKI Hub installations on Cryptographic Security Platform 1.5.0.

Unexpected error when deploying Certificate Authority (ATEAM-19407)

Due to a concurrency issue, Certificate Authority deployment may fail and log an “invalid variable name” error.

To fix this issue, contact the Entrust support team as explained in Generating support reports.

Installations with Certificate Enrollment Gateway cannot be restored (CSF-704 & EDM-18536)

PKI Hub installations with a deployed Certificate Enrollment Gateway do not support Restoring PKI Hub.

Workaround:

  1. Contact Entrust support for a new version of the csf-backup-restore.sh script
  2. Open a user session in any of the PKI Hub installation nodes.
  3. Run the following commands to install the script. 
    sudo cp --force csf-backup-restore.sh /opt/entrust/scripts/rhel/
    sudo chmod 550 /opt/entrust/scripts/rhel/csf-backup-restore.sh
    sudo chown sysadmin:edm /opt/entrust/scripts/rhel/csf-backup-restore.sh
  4. Follow the steps described in Restoring PKI Hub to restore the state.

Occasional restore failures of single-node installations (EDM-16171)

The process described in Restoring PKI Hub fails 75% of the time on single-node installations.

Workaround: Run the clusterctl uninstall command to uninstall the cluster, and re-try Restoring PKI Hub.

NetworkManager configuration on Azure and AWS machines is removed after reboot (EDM-22093)

When upgrading a PKI Hub installation on AWS or Azure to Cryptographic Security Platform 1.4, network configuration changes made using NetworkManager tools such as nmcli or nmtui may be overwritten when the machine is rebooted.

Workaround: After upgrading to Cryptographic Security Platform 1.4 and rebooting the machine, perform the following steps.

  1. Verify the configuration of all network interfaces.
  2. Verify connectivity to required services and confirm that DNS resolution is working correctly.
  3. Reapply any required custom network configuration through the AWS or Azure platform, not directly on the virtual machine. Changes made on the virtual machine itself may be overwritten during subsequent reboots.