Merge pull request #3111 from CumulusNetworks/create-pull-request/patch

Changes by create-pull-request action

Author: mergify[bot]

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

@@ -171,6 +171,8 @@ pdfhidden: True
 
 |  Issue ID 	|   Description	|   Affects	|   Fixed |
 |---	        |---	        |---	    |---	                |
+| <a name="4875599"></a> [4875599](#4875599) <a name="4875599"></a> <br /> | When you configure authentication for a BGP dynamic neighbor, removing the configuration does not bring back the sessions. | 5.15.0-5.15.1 | |
+| <a name="4873853"></a> [4873853](#4873853) <a name="4873853"></a> <br /> | TACACS authentication is not working with flat files. The Cumulus Linux user guide is missing the <code>sudo pam-auth-update --enable tacplus</code> command. | 5.15.0-5.15.1 | |
 | <a name="4859201"></a> [4859201](#4859201) <a name="4859201"></a> <br /> | When the VNI changes on a VRF, from the old VNI to the new VNI, the VNI in the SVD VNI hash table or in the single‑VNI (SVD) in the VNI info is deleted. Therefore, when there are further updates to the old VNI, the lookup fails and causes the zebra core to crash.  | 5.14.0-5.15.1 | |
 | <a name="4850551"></a> [4850551](#4850551) <a name="4850551"></a> <br /> | The switch installs suboptimal routes in the routing table and advertises them out. | 5.9.2-5.15.1 | |
 | <a name="4850188"></a> [4850188](#4850188) <a name="4850188"></a> <br /> | Signal quality degradation is observed during SR4-100G to 4×25G breakout using an adapter. | 5.15.0-5.15.1 | |
@@ -193,6 +195,7 @@ pdfhidden: True
 | <a name="4781498"></a> [4781498](#4781498) <a name="4781498"></a> <br /> | When you use a text-based patch file with <code>nv config patch cmd.txt</code> or <code>nv config replace cmd.txt</code>, if the <code>cmd.txt</code> file contains any of the following CLI commands, the patch operation fails and triggers an exception in NVUE:<br><pre>nv set system aaa auth order radius <array><br>nv set system ssh-server ciphers <array><br>nv set system ssh-server macs <array><br>nv set system ssh-server kex-algorithms <array><br>nv set system ssh-server pubkey-accepted-algorithms <array><br>nv set system ssh-server host-key-algorithms <array></pre> <br>To work around this issue, use a YAML file instead of a text-based patch file or run the <code>nv set</code> commands manually. | 5.15.0-5.15.1 | |
 | <a name="4776471"></a> [4776471](#4776471) <a name="4776471"></a> <br /> | In Cumulus Linux 5.15.0, NTP and DNS configuration commands changed from <code>nv set service</code> to <code>nv set system</code>. However, after upgrading the switch to Cumulus Linux 5.15.1, the <code>nv set service</code> command might still appear in the configuration output because a stale <code>nv set service</code> command remains after the configuration is translated during the upgrade. If you save the configuration with the <code>nv config show -o commands</code>, then reapply the configuration with <code>nv config replace</code>, the command fails if the stale <code>nv set service</code> command is present.<br>To workaround this issue, before applying the configuration with <code>nv config replace</code>, remove any stale <code>nv set service</code> commands from the saved configuration file, then reapply the configuration with the <code>nv config replace <config-file></code> command. | 5.15.0-5.15.1 | |
 | <a name="4776470"></a> [4776470](#4776470) <a name="4776470"></a> <br /> | In Cumulus Linux 5.15.0, NTP and DNS configuration commands changed from <code>nv set service</code> to <code>nv set system</code>. However, after upgrading the switch to Cumulus Linux 5.15.1, the <code>nv set service</code> command might still appear in the configuration output because a stale <code>nv set service</code> command remains after the configuration is translated during the upgrade. If you save the configuration with the <code>nv config show -o commands</code>, then reapply the configuration with <code>nv config replace</code>, the command fails if the stale <code>nv set service</code> command is present.<br>To workaround this issue, before applying the configuration with <code>nv config replace</code>, remove any stale <code>nv set service</code> commands from the saved configuration file, then reapply the configuration with the <code>nv config replace <config-file></code> command. | 5.15.0-5.15.1 | |
+| <a name="4776444"></a> [4776444](#4776444) <a name="4776444"></a> <br /> | In rare cases when telemetry is configured on a switch with high interface scale, the following log message might be generated and lead to a kernel crash event:<br><pre>interface_stats_collector&#91;27979&#93;: ERROR intf_stats_collector.go:485 WaitBulkCounterDone error: unable to receive trap info after 15 iterations</pre> | 5.15.0-5.15.1 | |
 | <a name="4776390"></a> [4776390](#4776390) <a name="4776390"></a> <br /> | gNMI subscription changes for interface counters, buffer, packet trim, latency or any other statistics produced by the <code>prometheus-sdk-stats</code> service leads to a change in the service configuration file causing the load interval configuration to be removed. This results in a rate calculation done with an interval of 60s instead of the interval configured in NVUE. | 5.15.0-5.15.1 | |
 | <a name="4771875"></a> [4771875](#4771875) <a name="4771875"></a> <br /> | When you poll optical module data with <code>ethtool -m</code>, <code>switchd</code> might crash due to a firmware timeout that triggers a fatal health-check failure. | 5.11.1-5.15.1 | |
 | <a name="4771865"></a> [4771865](#4771865) <a name="4771865"></a> <br /> | When you change the RADIUS privilege level, all affected existing RADIUS users are not updated in the next session to the relevant privilege level. | 5.15.0-5.15.1 | |

content/cumulus-linux-515/rn.xml

@@ -961,6 +961,18 @@ cumulus@switch:~$ sudo ethtool -s swp1 speed 100000 autoneg off lanes 2
 <th> Fixed </th>
 </tr>
 <tr>
+<td>4875599</td>
+<td>When you configure authentication for a BGP dynamic neighbor, removing the configuration does not bring back the sessions.</td>
+<td>5.15.0-5.15.1</td>
+<td></td>
+</tr>
+<tr>
+<td>4873853</td>
+<td>TACACS authentication is not working with flat files. The Cumulus Linux user guide is missing the {{sudo pam-auth-update --enable tacplus}} command.</td>
+<td>5.15.0-5.15.1</td>
+<td></td>
+</tr>
+<tr>
 <td>4859201</td>
 <td>When the VNI changes on a VRF, from the old VNI to the new VNI, the VNI in the SVD VNI hash table or in the single‑VNI (SVD) in the VNI info is deleted. Therefore, when there are further updates to the old VNI, the lookup fails and causes the zebra core to crash. </td>
 <td>5.14.0-5.15.1</td>
@@ -1105,6 +1117,15 @@ To work around this issue, use a YAML file instead of a text-based patch file or
 <td></td>
 </tr>
 <tr>
+<td>4776444</td>
+<td>In rare cases when telemetry is configured on a switch with high interface scale, the following log message might be generated and lead to a kernel crash event:
+
+interface_stats_collector[27979]: ERROR intf_stats_collector.go:485 WaitBulkCounterDone error: unable to receive trap info after 15 iterations
+</td>
+<td>5.15.0-5.15.1</td>
+<td></td>
+</tr>
+<tr>
 <td>4776390</td>
 <td>gNMI subscription changes for interface counters, buffer, packet trim, latency or any other statistics produced by the {{prometheus-sdk-stats}} service leads to a change in the service configuration file causing the load interval configuration to be removed. This results in a rate calculation done with an interval of 60s instead of the interval configured in NVUE.</td>
 <td>5.15.0-5.15.1</td>