20. Release Notes

20.1. Robin Cloud Native Storage v5.4.18-221

The Robin CNS v5.4.18-221 Release Notes document provides information about upgrade paths, an improvement, and fixed issues.

Release Date: September 05, 2025

20.1.1. Upgrade Paths

The following are the supported upgrade paths for Robin CNS v5.4.18-221:

  • Robin CNS v5.4.16-105 to Robin CNS v5.4.18-221

  • Robin CNS v5.4.8-280 to Robin CNS v5.4.18-221

Note

  • After upgrading to Robin CNS v5.4.18-221, if you are using the Robin Client outside the robincli Pod, you must upgrade to the latest version of the Robin Client.

  • If you have installed Robin CNS with the skip_postgres_operator parameter to use the Zalando PostgreSQL operator, then you must first upgrade the Zalando PostgreSQL operator to v1.11.0 or later before upgrading to Robin CNS v5.4.18-221.

  • After upgrading from any supported Robin CNS version, starting with Robin CNS v5.4.18, certificates will be automatically renewed.

20.1.2. Improvement

20.1.2.1. Readiness probe support for IOMGR service

Starting with Robin CNS v5.4.18, Robin CNS introduces Readiness probe support for the IOMGR service. These probes verify that both RIO and RDVM services are operational and ready to serve I/O operations. When both services are ready, then only Robin CNS marks the IOMGR service as ready. For more information about Readiness probe, see Readiness probe.

20.1.3. Fixed Issues

Reference ID

Description

RSD-9809, RSD-10087

The out-of-sync issue with Patroni Pods that led to a Robin Service Outage is fixed.

RSD-9861, RSD-9886, RSD-9944

The RPC client is dropping pending I/O requests without processing the received response. The SyncVMI issue is fixed.

RSD-9882

The issue of IOMgr failing to restart the volume remount operation once the STORMgr recovers from failure is fixed.

RSD-9867

The issue of creating a thick clone volume from its snapshot was getting stuck in hydrating state is fixed.

RSD-9775

The Robin CNS v5.4.16 installation failed because the robin-patroni-pre-install-hook job did not execute successfully, leaving Patroni stale data. This is caused by one of its Pods stuck in the CreateContainerError state during the installation. This issue is fixed.

RSD-9603

When a node with an active master Pod is rebooted, in the kubectl describe robinclusters command output, the Phase field shows the correct status of the Robin CNS cluster as NotReady, but the phase_reason field is empty. This issue is fixed.

RSD-9518

The Sherlock tool is incorrectly reporting one of the nodes as down. This issue is fixed by removing the SSH service from its diagnostic checks.

RSD-9422

In a rare scenario, when a thick clone volume hydration is in progress, if that clone volume’s PVC is deleted, stormgr-server goes down, and as a result another thick clone volume’s hydration gets stuck. This issue is fixed.

RSD-7375

The volume populators feature is not working as expected in the Robin CNS v5.4.8. This issue is fixed.

RSD-9165

When a node is removed and added back to the cluster, Robin Patroni Pods are stuck in the Pending state on that node, as required labels were not added to the replaced node. This issue is fixed.

RSD-9654

In a rare scenario, IO operations hung up on the Robin volume slice due to a network blip. This issue is fixed.

RSD-10021

If the robin-patroni-0 Pod gets stuck in a Pending or Terminating state due to maintenance or a node failure, the other Robin Patroni replicas cannot be scheduled, as the Robin Patroni StatefulSet is configured with the OrderedReady Pod management policy, which creates Pods sequentially. As a result, the Robin API server becomes unavailable. This issue is fixed by setting the Pod management policy to Parallel, which allows Pods to be created concurrently.

PP-38537

After deleting a backup, unregistering a storage repo fails with the following error message:

Storage repo is associated with volume group

This issue is fixed.

20.1.4. Technical Support

Contact Robin Technical support for any assistance.