The following issues have been addressed in the Mirantis Container Cloud release 2.4.0 and the Cluster releases 5.11.0 and 6.10.0:
 [BM] [IPAM] Fixed the issue with the automatically allocated subnet having the ability to requeue allocation from a
 [BM] [Ceph] Fixed the issue with OpenStack services failing to access
rook-ceph-mon-*pods due to the changed metadata for connection after pods restart if Ceph was deployed without
 [IAM] Fixed the issue with IAM failing to start with the IAM pods being in the
CrashLoopBackOffstate during a management cluster deployment.
 [IAM] Disabled the
httpport in Keycloak to prevent security vulnerabilities.
 [LCM] Fixed the issue with accidental upgrade of the
containerd.iopackages that must be pinned during the host OS upgrade.
 [LCM] Fixed the issue with error handling in the
 [LCM] Fixed the issue with Keepalived and NGINX being installed on worker nodes instead of being installed on control plane nodes only.
 [UI] Fixed the issue with offline tokens being expired over time if fetched using the Container Cloud web UI. The issue occurred if the Log in with Keycloak option was used.
 [UI] Fixed the issue with the “invalid_grant”,”error_description”: “Session doesn’t have required client” error occurring over time after logging in to the Container Cloud web UI through Log in with Keycloak.
 [UI] Fixed the issue with the SSH Keys dialog becoming blank after the token expiration.
 [UI] Fixed the issue with the previously selected Ceph cluster machines disappearing from the drop-down menu of the Create New Ceph Cluster dialog.
 [UI] Fixed the issue with Provider Credentials being stuck in the
Processingstate if created using the Add new credential option of the Create New Cluster dialog.