Addressed issues

The following issues have been addressed in the Mirantis Container Cloud release 2.15.0 along with the Cluster releases 7.5.0 and 5.22.0:

  • vSphere:

    • [19737] Fixed the issue with the vSphere VM template build hanging with an empty kickstart file on the vSphere deployments with the RHEL 8.4 seed node.

    • [19468] Fixed the issue with the ‘Failed to remove finalizer from machine’ error during cluster deletion if a RHEL license is removed before the related managed cluster was deleted.

  • IAM:

    • [5025] Updated the Keycloak version from 12.0.0 to 15.0.2 to fix the CVE-2020-2757.

    • [21024][Custom certificates] Fixed the issue with the readiness check failure during addition of a custom certificate for Keycloak that hung with the failed to wait for OIDC certificate to be updated timeout warning.

  • StackLight:

    • [20193] Updated the Grafana Docker image from 8.2.2 to 8.2.7 to fix the high-severity CVE-2021-43798.

    • [18933] Fixed the issue with the Alerta pods failing to pass the readiness check even if Patroni, the Alerta back end, operated correctly.

    • [19682] Fixed the issue with the Prometheus web UI URLs in notifications sent to Salesforce using the HTTP protocol instead of HTTPS on deployments with TLS enabled for IAM.

  • Ceph:

    • [19645] Fixed the issue with the Ceph OSD removal request failure during the Processing stage.

    • [19574] Fixed the issue with the Ceph OSD removal not cleaning up the device used for multiple OSDs.

    • [20298] Fixed the issue with spec validation failing during creation of KaaSCephOperationRequest.

    • [20355] Fixed the issue with KaaSCephOperationRequest being cached after recreation with the same name, specified in metadata.name, as the previous KaaSCephOperationRequest CR. The issue caused no removal to be performed upon applying the new KaaSCephOperationRequest CR.

  • Bare metal:

    • [19786] Fixed the issue with managed cluster deployment failing on long-running management clusters with BareMetalHost being stuck in the Preparing state and the ironic-conductor and ironic-api pods reporting the not enough disk space error due to the dnsmasq-dhcpd logs overflow.

  • Upgrade:

    • [20459] Fixed the issue with failure to upgrade a management or regional cluster originally deployed using the Container Cloud release earlier than 2.8.0. The failure occurred during Ansible update if a machine contained /usr/local/share/ca-certificates/mcc.crt, which was either empty or invalid.