Skip to content

Changes by create-pull-request action #3408

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mergify merged 1 commit into from
Aug 31, 2026
Merged

Changes by create-pull-request action #3408

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 22 additions & 18 deletions content/cumulus-linux-516/Whats-New/rn.md
View file
Open in desktop

Large diffs are not rendered by default.

126 changes: 75 additions & 51 deletions content/cumulus-linux-516/rn.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@
<th> Fixed </th>
</tr>
<tr>
<td>5240456</td>
<td>BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show {{nexthop_set failed with remote: (null) and Transport endpoint is not...}}.</td>
<td>5.16.1, 5.16.5-5.18.0</td>
<td></td>
</tr>
<tr>
<td>5225576, 5236486</td>
<td>After an optimized image upgrade from Cumulus Linux 5.13.1 or earlier to a later release, the install step fails with a permission error if the image being installed is already present in the {{/var/images}} directory before the upgrade. In this state, the {{nv show system image files}} command might not list any images. To work around this issue, fetch the image with the {{nv action fetch system image &lt;remote-url&gt;}} command before installing it. Alternatively, correct the directory permissions with {{sudo chmod 0755 /var/images}}.</td>
<td>5.16.6-5.18.0</td>
Expand All @@ -19,18 +25,6 @@
<td></td>
</tr>
<tr>
<td>5221592</td>
<td>Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures.</td>
<td>5.16.5-5.18.0</td>
<td></td>
</tr>
<tr>
<td>5221589</td>
<td>In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export.</td>
<td>5.16.5-5.18.0</td>
<td></td>
</tr>
<tr>
<td>5217147, 5225676</td>
<td>When you perform a factory reset after an optimized image upgrade, the switch loses record of its model information.</td>
<td>5.16.6-5.18.0</td>
Expand Down Expand Up @@ -638,6 +632,12 @@ where only the aggregate should be advertised.</td>
<td>5.17.0-5.18.0</td>
</tr>
<tr>
<td>4850225</td>
<td>The NVUE {{nv show even vin &lt;vni-id&gt;}} command and the vtysh {{show evpn vni &lt;vni-id&gt;}} command do not display VLAN information for newly added VNIs.</td>
<td>5.16.0-5.16.1, 5.16.5-5.16.7</td>
<td>5.17.0-5.18.0</td>
</tr>
<tr>
<td>4841491</td>
<td>When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1.</td>
<td>5.16.0-5.16.1, 5.16.5-5.18.0</td>
Expand Down Expand Up @@ -1436,7 +1436,7 @@ cumulus@switch:~$ sudo ethtool -s swp1 speed 100000 autoneg off lanes 2
<td>5.16.5-5.16.6</td>
</tr>
<tr>
<td>5221130</td>
<td>5221130, 5221589</td>
<td>When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail.</td>
<td>5.16.5-5.16.6</td>
</tr>
Expand All @@ -1461,7 +1461,7 @@ cumulus@switch:~$ sudo ethtool -s swp1 speed 100000 autoneg off lanes 2
<td>5.16.0-5.16.1, 5.16.5-5.16.6</td>
</tr>
<tr>
<td>5217101</td>
<td>5217101, 5221592</td>
<td>AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages:

switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18
Expand Down Expand Up @@ -1522,19 +1522,7 @@ switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive
<td></td>
</tr>
<tr>
<td>5221592</td>
<td>Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures.</td>
<td>5.16.5-5.18.0</td>
<td></td>
</tr>
<tr>
<td>5221589</td>
<td>In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export.</td>
<td>5.16.5-5.18.0</td>
<td></td>
</tr>
<tr>
<td>5221130</td>
<td>5221130, 5221589</td>
<td>When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail.</td>
<td>5.16.5-5.16.6</td>
<td>5.16.7-5.18.0</td>
Expand All @@ -1546,7 +1534,7 @@ switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive
<td></td>
</tr>
<tr>
<td>5217101</td>
<td>5217101, 5221592</td>
<td>AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages:

switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18
Expand Down Expand Up @@ -1576,6 +1564,12 @@ switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive
<td></td>
</tr>
<tr>
<td>5197572, 5183241</td>
<td>In rare cases, you cannot cancel bulk counter session(MOCS), which results in missing GNMI metrics during export. To work around this issue, reboot the switch.</td>
<td>5.16.5-5.16.6</td>
<td>5.16.7-5.18.0</td>
</tr>
<tr>
<td>5183514, 5217107, 5221591</td>
<td>The NVUE set command returns a traceback in the output when the per user repo_incarnation file ({{/home/$USER/.local/share/nvue/repo_incarnation}}) is non-writable.</td>
<td>5.16.1, 5.16.5-5.16.6</td>
Expand All @@ -1591,7 +1585,7 @@ Pin-Priority: 992</td>
<td></td>
</tr>
<tr>
<td>5182789, 5217108, 5221590, 5216045, 5215790</td>
<td>5182789, 5217108, 5221590, 5216045, 5215790, 5240456</td>
<td>BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show {{nexthop_set failed with remote: (null) and Transport endpoint is not...}}.</td>
<td>5.16.1, 5.16.5-5.16.6</td>
<td>5.16.7-5.18.0</td>
Expand All @@ -1603,6 +1597,12 @@ Pin-Priority: 992</td>
<td>5.16.7-5.18.0</td>
</tr>
<tr>
<td>5179104</td>
<td>Adaptive routing ECMP updates during route deletion might sometimes result in ECMP database corruption followed by ECMP operation failures.</td>
<td>5.16.5-5.16.6</td>
<td>5.16.7-5.18.0</td>
</tr>
<tr>
<td>5175518, 5217093, 5221594</td>
<td>The {{switchd}} watchdog crashes due to a netlink buffer overflow triggered by continuous next hop group churn.</td>
<td>5.16.1, 5.16.5-5.16.6, 5.18.0</td>
Expand Down Expand Up @@ -2219,6 +2219,12 @@ where only the aggregate should be advertised.</td>
<td>5.17.0-5.18.0</td>
</tr>
<tr>
<td>4850225</td>
<td>The NVUE {{nv show even vin &lt;vni-id&gt;}} command and the vtysh {{show evpn vni &lt;vni-id&gt;}} command do not display VLAN information for newly added VNIs.</td>
<td>5.16.0-5.16.1, 5.16.5-5.16.7</td>
<td>5.17.0-5.18.0</td>
</tr>
<tr>
<td>4841491</td>
<td>When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1.</td>
<td>5.16.0-5.16.1, 5.16.5-5.18.0</td>
Expand Down Expand Up @@ -3089,8 +3095,8 @@ Workaround: Restarting switchd temporarily restores metrics.</td>
<td>5.16.1, 5.16.5</td>
</tr>
<tr>
<td>5145959</td>
<td>During a switch reboot with SRv6 enabled, there is an ordering race that occasionally results in the {{nginx-authenticator.service}} only listening on the IPv6 loopback IP address. As result, the gNMI server Envoy instance, which uses the {{nginx-authenticator.service}} to validate the username and password in requests from the gNMI client fails to connect and you see the error {{rpc error: code = Unavailable desc = Authentication service unavailable}}.</td>
<td>5145959, 5142608</td>
<td>A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the {{nginx-authenticator}} service to authenticate users if SRv6 is enabled. This occurs if the {{nginx-authenticator}} service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address.</td>
<td>5.16.1, 5.16.5</td>
</tr>
<tr>
Expand All @@ -3113,25 +3119,13 @@ Workaround: Restarting switchd temporarily restores metrics.</td>
<td></td>
</tr>
<tr>
<td>5221592</td>
<td>Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures.</td>
<td>5.16.5-5.18.0</td>
<td></td>
</tr>
<tr>
<td>5221589</td>
<td>In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export.</td>
<td>5.16.5-5.18.0</td>
<td></td>
</tr>
<tr>
<td>5221130</td>
<td>5221130, 5221589</td>
<td>When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail.</td>
<td>5.16.5-5.16.6</td>
<td>5.16.7-5.18.0</td>
</tr>
<tr>
<td>5217101</td>
<td>5217101, 5221592</td>
<td>AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages:

switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18
Expand All @@ -3155,6 +3149,12 @@ switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive
<td></td>
</tr>
<tr>
<td>5197572, 5183241</td>
<td>In rare cases, you cannot cancel bulk counter session(MOCS), which results in missing GNMI metrics during export. To work around this issue, reboot the switch.</td>
<td>5.16.5-5.16.6</td>
<td>5.16.7-5.18.0</td>
</tr>
<tr>
<td>5183514, 5217107, 5221591</td>
<td>The NVUE set command returns a traceback in the output when the per user repo_incarnation file ({{/home/$USER/.local/share/nvue/repo_incarnation}}) is non-writable.</td>
<td>5.16.1, 5.16.5-5.16.6</td>
Expand All @@ -3170,7 +3170,7 @@ Pin-Priority: 992</td>
<td></td>
</tr>
<tr>
<td>5182789, 5217108, 5221590, 5216045, 5215790</td>
<td>5182789, 5217108, 5221590, 5216045, 5215790, 5240456</td>
<td>BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show {{nexthop_set failed with remote: (null) and Transport endpoint is not...}}.</td>
<td>5.16.1, 5.16.5-5.16.6</td>
<td>5.16.7-5.18.0</td>
Expand All @@ -3182,6 +3182,12 @@ Pin-Priority: 992</td>
<td>5.16.7-5.18.0</td>
</tr>
<tr>
<td>5179104</td>
<td>Adaptive routing ECMP updates during route deletion might sometimes result in ECMP database corruption followed by ECMP operation failures.</td>
<td>5.16.5-5.16.6</td>
<td>5.16.7-5.18.0</td>
</tr>
<tr>
<td>5175518, 5217093, 5221594</td>
<td>The {{switchd}} watchdog crashes due to a netlink buffer overflow triggered by continuous next hop group churn.</td>
<td>5.16.1, 5.16.5-5.16.6, 5.18.0</td>
Expand Down Expand Up @@ -3260,8 +3266,8 @@ Pin-Priority: 992</td>
<td>5.16.6-5.18.0</td>
</tr>
<tr>
<td>5145959</td>
<td>During a switch reboot with SRv6 enabled, there is an ordering race that occasionally results in the {{nginx-authenticator.service}} only listening on the IPv6 loopback IP address. As result, the gNMI server Envoy instance, which uses the {{nginx-authenticator.service}} to validate the username and password in requests from the gNMI client fails to connect and you see the error {{rpc error: code = Unavailable desc = Authentication service unavailable}}.</td>
<td>5142608, 5145959</td>
<td>A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the {{nginx-authenticator}} service to authenticate users if SRv6 is enabled. This occurs if the {{nginx-authenticator}} service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address.</td>
<td>5.16.1, 5.16.5</td>
<td>5.16.6-5.18.0</td>
</tr>
Expand Down Expand Up @@ -3908,6 +3914,12 @@ where only the aggregate should be advertised.</td>
<td>5.17.0-5.18.0</td>
</tr>
<tr>
<td>4850225</td>
<td>The NVUE {{nv show even vin &lt;vni-id&gt;}} command and the vtysh {{show evpn vni &lt;vni-id&gt;}} command do not display VLAN information for newly added VNIs.</td>
<td>5.16.0-5.16.1, 5.16.5-5.16.7</td>
<td>5.17.0-5.18.0</td>
</tr>
<tr>
<td>4841491</td>
<td>When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1.</td>
<td>5.16.0-5.16.1, 5.16.5-5.18.0</td>
Expand Down Expand Up @@ -4869,7 +4881,7 @@ kernel: [899873.236610] sxd_kernel: dev_id=1: Health-Check: New maximum time bet
<td>5.16.7-5.18.0</td>
</tr>
<tr>
<td>5182789, 5217108, 5221590, 5216045, 5215790</td>
<td>5182789, 5217108, 5221590, 5216045, 5215790, 5240456</td>
<td>BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show {{nexthop_set failed with remote: (null) and Transport endpoint is not...}}.</td>
<td>5.16.1, 5.16.5-5.16.6</td>
<td>5.16.7-5.18.0</td>
Expand Down Expand Up @@ -4929,8 +4941,8 @@ kernel: [899873.236610] sxd_kernel: dev_id=1: Health-Check: New maximum time bet
<td>5.16.6-5.18.0</td>
</tr>
<tr>
<td>5145959</td>
<td>During a switch reboot with SRv6 enabled, there is an ordering race that occasionally results in the {{nginx-authenticator.service}} only listening on the IPv6 loopback IP address. As result, the gNMI server Envoy instance, which uses the {{nginx-authenticator.service}} to validate the username and password in requests from the gNMI client fails to connect and you see the error {{rpc error: code = Unavailable desc = Authentication service unavailable}}.</td>
<td>5142608, 5145959</td>
<td>A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the {{nginx-authenticator}} service to authenticate users if SRv6 is enabled. This occurs if the {{nginx-authenticator}} service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address.</td>
<td>5.16.1, 5.16.5</td>
<td>5.16.6-5.18.0</td>
</tr>
Expand Down Expand Up @@ -5680,6 +5692,12 @@ where only the aggregate should be advertised.</td>
<td>5.17.0-5.18.0</td>
</tr>
<tr>
<td>4850225</td>
<td>The NVUE {{nv show even vin &lt;vni-id&gt;}} command and the vtysh {{show evpn vni &lt;vni-id&gt;}} command do not display VLAN information for newly added VNIs.</td>
<td>5.16.0-5.16.1, 5.16.5-5.16.7</td>
<td>5.17.0-5.18.0</td>
</tr>
<tr>
<td>4841491</td>
<td>When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1.</td>
<td>5.16.0-5.16.1, 5.16.5-5.18.0</td>
Expand Down Expand Up @@ -7146,6 +7164,12 @@ where only the aggregate should be advertised.</td>
<td>5.17.0-5.18.0</td>
</tr>
<tr>
<td>4850225</td>
<td>The NVUE {{nv show even vin &lt;vni-id&gt;}} command and the vtysh {{show evpn vni &lt;vni-id&gt;}} command do not display VLAN information for newly added VNIs.</td>
<td>5.16.0-5.16.1, 5.16.5-5.16.7</td>
<td>5.17.0-5.18.0</td>
</tr>
<tr>
<td>4841491</td>
<td>When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1.</td>
<td>5.16.0-5.16.1, 5.16.5-5.18.0</td>
Expand Down
Loading