See below for the PKI Hub bugs fixed in Cryptographic Security Platform 1.5.0.

Error while checking disk performance (EDM-21420)

The installation process could fail during fio disk performance checks with a "No such file or directory" error.

New kernels do not boot (EDM-21636)

Cloud images failed to boot newly installed kernels because the boot loader entries retained the placeholder machine ID used at build time.

Incorrect default kernel setting on cloud images (EDM-21678)

Cloud images incorrectly set DEFAULTKERNEL to kernel-uek instead of kernel-uek-core, preventing GRUB from updating the default boot entry after a kernel upgrade.

Registry Persistent Volume Grows Indefinitely (EDM-21782)

Docker registry garbage collection does not remove untagged manifests, causing the registry persistent volume to grow indefinitely.

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.

Disabled users can open SSH sessions (EDM-22662)

Users disabled with the clusterctl node user modify command can still log in to the appliance through SSH.