Release Notes ############# Robin Cloud Native Storage v5.4.16-105 ************************************** The Robin CNS v5.4.16-105 Release Notes document provides information about upgrade paths, a new feature, an improvement, fixed issues, and a known issue. **Release Date:** April 16, 2025 Upgrade Paths ============== The following are the supported upgrade paths for Robin CNS v5.4.16-105: - Robin CNS v5.4.14-63 to Robin CNS v5.4.16-105 - Robin CNS v5.4.8-280 to Robin CNS v5.4.16-105 .. Note:: - After upgrading to Robin CNS v5.4.16-105, 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.16-105. New Features ============ Patroni with failsafe mode enabled ----------------------------------- Starting with Robin CNS v5.4.16, by default the ``failsafe`` mode is enabled in Patroni 3.2.2. The ``failsafe`` mode prevents the Patroni leader from demoting itself during temporary network disruptions or when it loses access to the Kubernetes control plane or etcd. It ensures continuous database availability by having uninterrupted communication with other Patroni replicas. However, even when the ``failsafe`` mode is enabled, the Patroni leader will demote itself in the following scenarios: - Network partitions - DCS is down .. pp-38119 Improvements ============= New Volume Metrics ------------------- .. PP-37808 and PP-36704 Starting with Robin CNS v5.4.16, the following two new metrics are introduced. a new metric, ``robin_vol_psize`` is introduced. - ``robin_vol_psize`` - ``robin_vol_serving`` **robin_vol_psize** It represents the physical (or raw) storage space (in bytes) used by a single replica of the volume. This the metric provides further insight into storage consumption. **Example:** .. code-block:: text [robinmaster@master ~]# curl -k https://localhost:29446/metrics robin_vol_rawused{name="pvc-89382d8e-66c4-4d42-8d8c-62f7a328c713",volid="2"} 134217728 robin_vol_size{name="pvc-89382d8e-66c4-4d42-8d8c-62f7a328c713",volid="2"} 1073741824 robin_vol_psize{name="pvc-89382d8e-66c4-4d42-8d8c-62f7a328c713",volid="2"} 67108864 In the above output, the value ``67108864`` for ``robin_vol_psize`` represents the physical (or raw) storage space (in bytes) used by a single replica of the volume. **robin_vol_serving** The ``robin_vol_serving`` metric reflects the health of volume replicas and whether the volume replicas are in sync, serving read and write operations. The metric ``robin_vol_serving`` displays the following statuses: - Status ``0`` = Unknown - Status ``1`` = Serving - Status ``2`` = Degraded - Status ``3`` = Not Serving **Example:** .. code-block:: text robin_vol_serving{name="pvc-fad3245e-3a8c-42ab-a2ae-2b290bf450da",volid="5160"} 1 Fixed Issues ============= ============= ======================================================================================================================= Reference ID Description ============= ======================================================================================================================= RSD-8821 The ``robin_vol_total_snapshot_count`` metric is incorrectly displaying the snapshot count as 1 even though there are no snapshots. This issue is fixed. RSD-8378 Several vulnerabilities related to Apache server is fixed. RSD-9247 Volume detach and attach operations may take longer than expected after a node disconnection event, such as a node power-off or network disconnect. This issue is fixed. ============= ======================================================================================================================= Known Issues ============= ============= ======================================================================================================================= Reference ID Description ============= ======================================================================================================================= PP-38537 **Symptom** After deleting a backup, unregistering a storage repo fails with the following error message: *Storage repo is associated with volume group* **Workaround** Complete the following steps: 1. Attach the repo to the App. .. code-block:: text # robin app attach-repo 2. Detach the repo from the App. .. code-block:: text # robin app detach-repo 3. Unregister the repo. .. code-block:: text # robin repo unregister ============= ======================================================================================================================= Technical Support ================= Contact `Robin Technical support `_ for any assistance.