Changes by create-pull-request action

content/cumulus-linux-518/Whats-New/rn.md

@@ -27,7 +27,7 @@ pdfhidden: True
 | 5197214 | If the <code>cumulus-platform-common</code> package is updated, login notification might fail on each login and show errors. | 5.18.0 | |
 | 5190122 | On a Spectrum-6 switch (such as the SN6600-LD), gNMI reports an incorrect shared-buffer cell size of 192 bytes at <code>/qos/shared-buffer/state/cell-size</code> instead of the correct 256 bytes for Spectrum-6. Because this cell size is used to convert internal buffer cell counts into byte values, several shared-buffer telemetry values derived from it (such as per-queue or traffic-class buffer usage and maximum occupancy) report incorrectly over gNMI. The values are inconsistent with the values that NVUE reports and the hardware buffer counters. | 5.18.0 | |
 | 5184005 | In certain SRv6 configuration rollback scenarios, Zebra might fail to restore all explicit SRv6 SIDs. This can occur when multiple SRv6 locators share the same parent SID block and one of the locators is replayed during rollback. To work around this issue, restart FRR to clear the stale in-memory SRv6 SID allocation state, then reapply the intended configuration if needed. | 5.18.0 | |
-| 5183654 | When you upgrade gNMI with package upgrade, the <code>nv-gnmi.service</code> fails and the switch collects a tech support bundle after the first step of the process (<code>nv action upgrade system packages to latest</code>. The package upgrade process triggers a switch reboot straight afterwards as a second and final step. There is no functional impact after switch reboot completes. | 5.18.0 | |
+| 5183654, 5234851 | When you upgrade gNMI with package upgrade, the <code>nv-gnmi.service</code> fails and the switch collects a tech support bundle after the first step of the process (<code>nv action upgrade system packages to latest</code>. The package upgrade process triggers a switch reboot straight afterwards as a second and final step. There is no functional impact after switch reboot completes. | 5.18.0 | |
 | 5183442 | If the running version of Cumulus Linux is not the newest, installing packages in <code>cumulus-local-apt-archive</code> (RADIUS or TACACS+ packages) might bring in a newer version from remote locations that does not match the running version of Cumulus Linux.  To avoid this problem add an <code>/etc/apt/preferences.d/10_prefer_cumulus_local_apt_archive</code> file with the following content (if not already present) before doing a package update:<br><pre>Package: *<br>Pin: release a=cumulus-local-apt-archive<br>Pin-Priority: 992</pre> | 5.16.5-5.18.0 | |
 | 5180032, 5180016 | Running a transceiver query with the <code>ethtool -m</code> or <code>nv show interface <interface> transceiver</code> command might intermittently discard the reply, causing the command to hang for approximately 30 seconds and fail with <code>netlink error: Connection timed out</code> before recovering. | 5.18.0 | |
 | 5175518, 5217093, 5221594 | The <code>switchd</code> watchdog crashes due to a netlink buffer overflow triggered by continuous next hop group churn. | 5.16.1, 5.16.5-5.16.6, 5.18.0 | 5.16.7|

content/cumulus-linux-518/rn.xml

@@ -85,7 +85,7 @@
 <td></td>
 </tr>
 <tr>
-<td>5183654</td>
+<td>5183654, 5234851</td>
 <td>When you upgrade gNMI with package upgrade, the {{nv-gnmi.service}} fails and the switch collects a tech support bundle after the first step of the process ({{nv action upgrade system packages to latest}}. The package upgrade process triggers a switch reboot straight afterwards as a second and final step. There is no functional impact after switch reboot completes.</td>
 <td>5.18.0</td>
 <td></td>