Automated release note commit

CumulusNetworks · Nov 20, 2024 · 4ac7e63 · 4ac7e63
1 parent 67c3917
commit 4ac7e63
Show file tree

Hide file tree

Showing 4 changed files with 16 additions and 16 deletions.
diff --git a/content/cumulus-linux-510/Whats-New/rn.md b/content/cumulus-linux-510/Whats-New/rn.md
@@ -14,10 +14,10 @@ pdfhidden: True
 
 |  Issue ID 	|   Description	|   Affects	|   Fixed |
 |---	        |---	        |---	    |---	                |
+| <a name="4175217"></a> [4175217](#4175217) <a name="4175217"></a> <br /> | When there is a large number of discontiguous VTEP to VLAN mappings, <code>switchd</code> crashes with a Netlink error similar to the following:<pre><br>netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message</pre> | 5.10.1-5.11.0 | |
 | <a name="4173498"></a> [4173498](#4173498) <a name="4173498"></a> <br /> | After network churn, the <code>watchfrr</code> process might restart FRR because zebra is unresponsive. | 5.9.1-5.11.0 | |
 | <a name="4170628"></a> [4170628](#4170628) <a name="4170628"></a> <br /> | If you use a bridge name that isn't <code>br_default</code>, NVUE generates incorrect ptp4l.conf files. | 5.10.0-5.11.0 | |
 | <a name="4170598"></a> [4170598](#4170598) <a name="4170598"></a> <br /> | When you create an ACL rule that matches TCP state and more than seven TCP or UDP source or destination ports, the rule does not get framed properly and is rejected by the kernel.<br>To work around this issue, create another rule number when the number of ports you want to match is more than seven. | 5.9.1-5.11.0 | |
-| <a name="4150508"></a> [4150508](#4150508) <a name="4150508"></a> <br /> | When there is a large number of discontiguous VTEP to VLAN mappings, <code>switchd</code> crashes with a Netlink error similar to the following:<pre><br>netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message</pre> | 5.10.1-5.11.0 | |
 | <a name="4142857"></a> [4142857](#4142857) <a name="4142857"></a> <br /> | The switch drops PTP packets received with extra ethernet padding and you see syslog <code>&#91;ptp4l.ERR&#93; messages. | 5.10.0-5.11.0 | |
 | <a name="4137492"></a> [4137492](#4137492) <a name="4137492"></a> <br /> | Accessing NVIDIA Spectrum-4 SPICE from multiple applications to the same path in parallel might cause a kernel crash. | 5.10.1 | 5.11.0|
 | <a name="4135919"></a> [4135919](#4135919) <a name="4135919"></a> <br /> | You might experience a memory leak in <code>ospfd</code> when processing next hops due to network changes. | 5.9.1-5.11.0 | |

diff --git a/content/cumulus-linux-510/rn.xml b/content/cumulus-linux-510/rn.xml
@@ -7,6 +7,13 @@
 <th> Fixed </th>
 </tr>
 <tr>
+<td>4175217</td>
+<td>When there is a large number of discontiguous VTEP to VLAN mappings, {{switchd}} crashes with a Netlink error similar to the following:
+netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message</td>
+<td>5.10.1-5.11.0</td>
+<td></td>
+</tr>
+<tr>
 <td>4173498</td>
 <td>After network churn, the {{watchfrr}} process might restart FRR because zebra is unresponsive.</td>
 <td>5.9.1-5.11.0</td>
@@ -25,13 +32,6 @@
 <td></td>
 </tr>
 <tr>
-<td>4150508</td>
-<td>When there is a large number of discontiguous VTEP to VLAN mappings, {{switchd}} crashes with a Netlink error similar to the following:
-netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message</td>
-<td>5.10.1-5.11.0</td>
-<td></td>
-</tr>
-<tr>
 <td>4142857</td>
 <td>The switch drops PTP packets received with extra ethernet padding and you see syslog {{[ptp4l.ERR] messages.</td>
 <td>5.10.0-5.11.0</td>

diff --git a/content/cumulus-linux-511/Whats-New/rn.md b/content/cumulus-linux-511/Whats-New/rn.md
@@ -14,8 +14,8 @@ pdfhidden: True
 
 |  Issue ID 	|   Description	|   Affects	|   Fixed |
 |---	        |---	        |---	    |---	                |
+| <a name="4175217"></a> [4175217](#4175217) <a name="4175217"></a> <br /> | When there is a large number of discontiguous VTEP to VLAN mappings, <code>switchd</code> crashes with a Netlink error similar to the following:<pre><br>netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message</pre> | 5.10.1-5.11.0 | |
 | <a name="4170628"></a> [4170628](#4170628) <a name="4170628"></a> <br /> | If you use a bridge name that isn't <code>br_default</code>, NVUE generates incorrect ptp4l.conf files. | 5.10.0-5.11.0 | |
-| <a name="4150508"></a> [4150508](#4150508) <a name="4150508"></a> <br /> | When there is a large number of discontiguous VTEP to VLAN mappings, <code>switchd</code> crashes with a Netlink error similar to the following:<pre><br>netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message</pre> | 5.10.1-5.11.0 | |
 | <a name="4142857"></a> [4142857](#4142857) <a name="4142857"></a> <br /> | The switch drops PTP packets received with extra ethernet padding and you see syslog <code>&#91;ptp4l.ERR&#93; messages. | 5.10.0-5.11.0 | |
 | <a name="4135543"></a> [4135543](#4135543) <a name="4135543"></a> <br /> | Under certain rare scenarios, the operational status of a switch port interface shows as <code>UP</code> after you administratively configure it to stay down with the <code>nv set interface <interface> link status down</code> command. To clear this condition, toggle the admin status on the interface once. | 5.11.0 | |
 | <a name="4134174"></a> [4134174](#4134174) <a name="4134174"></a> <br /> | If you configure a route map by attaching it to a specific protocol, then you detach it from that protocol, if you then attach the same route map to all protocols, then detach it from all protocols, Cumulus Linux deletes routes from the forwarding table.<br>To work around this issue, either attach the route map to all protocols or attach the route map to each protocol you want to use. For example, to attach the route map to all protocols, run the <code>nv set vrf <vrf-name> router rib fib-filter route-map <route-map></code> command. To attach the route map to each protocol you want to use, run the <code>nv set vrf <vrf-name> router rib fib-filter protocol <protocol string> route-map <route-map></code> command. | 5.11.0 | |

diff --git a/content/cumulus-linux-511/rn.xml b/content/cumulus-linux-511/rn.xml
@@ -7,19 +7,19 @@
 <th> Fixed </th>
 </tr>
 <tr>
-<td>4170628</td>
-<td>If you use a bridge name that isn't {{br_default}}, NVUE generates incorrect ptp4l.conf files.</td>
-<td>5.10.0-5.11.0</td>
-<td></td>
-</tr>
-<tr>
-<td>4150508</td>
+<td>4175217</td>
 <td>When there is a large number of discontiguous VTEP to VLAN mappings, {{switchd}} crashes with a Netlink error similar to the following:
 netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message</td>
 <td>5.10.1-5.11.0</td>
 <td></td>
 </tr>
 <tr>
+<td>4170628</td>
+<td>If you use a bridge name that isn't {{br_default}}, NVUE generates incorrect ptp4l.conf files.</td>
+<td>5.10.0-5.11.0</td>
+<td></td>
+</tr>
+<tr>
 <td>4142857</td>
 <td>The switch drops PTP packets received with extra ethernet padding and you see syslog {{[ptp4l.ERR] messages.</td>
 <td>5.10.0-5.11.0</td>