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

Changes by create-pull-request action

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

@@ -72,7 +72,7 @@ pdfhidden: True
 | <a name="3378733"></a> [3378733](#3378733) <a name="3378733"></a> <br /> | After you add or delete a static MAC entry on the bridge FDB, a core dump occurs if the interface is VXLAN and the MAC address is 00:00:00:00:00:00. | 5.4.0-5.5.1 | 5.6.0|
 | <a name="3375047"></a> [3375047](#3375047) <a name="3375047"></a> <br /> | If you run the NVUE <code>nv set service snmp-server readonly-community</code> command to set an SNMP V2 trap community string that includes fewer than eight characters,  the configuration fails.  The SNMP V2 trap community string must include eight or more characters. | 5.4.0 | 5.5.0-5.6.0|
 | <a name="3368217"></a> [3368217](#3368217) <a name="3368217"></a> <br />None | When daylight saving time changes, the MLAG <code>initDelay</code> timer resets and all MLAG bonds go down. | 4.4.4-4.4.5, 5.2.1-5.6.0 | |
-| <a name="3362113"></a> [3362113](#3362113) <a name="3362113"></a> <br /> | If you restore an NVUE <code>startup.yaml</code> file after upgrade that includes breakout ports with QoS configuration or you run the <code>nv config patch</code> command to update a configuration with a <code>yaml</code> file that includes breakout ports with QoS configuration, the NVUE configuration fails to apply and subsequent attempts to run <code>nv config apply</code> fail with the following message: <pre>cumulus&#64;switch:~$ nv config applyInvalid config &#91;rev_id: 11&#93;<br /> qos config is not supported on following invalid interface: swp1s0. Supported on swp and bond interface types<br /></pre>To work around this issue, run <code>nv unset</code> on the configured QoS settings, then apply the breakout port configuration before you configure QoS. Alternatively, you can remove the QoS configuration from the <code>yaml</code> file and patch it separately after applying the breakout configuration. | 5.4.0-5.6.0 | |
+| <a name="3362113"></a> [3362113](#3362113) <a name="3362113"></a> <br /> | If you restore an NVUE <code>startup.yaml</code> file after upgrade that includes breakout ports with QoS configuration or you run the <code>nv config patch</code> command to update a configuration with a <code>yaml</code> file that includes breakout ports with QoS configuration, the NVUE configuration fails to apply and subsequent attempts to run <code>nv config apply</code> fail with the message similar to <code>Invalid config &#91;rev_id: 11&#93; qos config is not supported on following invalid interface: swp1s0. Supported on swp and bond interface types</code>. To work around this issue, run <code>nv unset</code> on the configured QoS settings, then apply the breakout port configuration before you configure QoS. Alternatively, you can remove the QoS configuration from the <code>yaml</code> file and patch it separately after applying the breakout configuration. | 5.4.0-5.6.0 | |
 | <a name="3361904"></a> [3361904](#3361904) <a name="3361904"></a> <br /> | The NVUE PTP shaping commands are available in the NVUE command list; however, these commands are disabled and do not configure PTP shaping. PTP shaping is not supported in Cumulus Linux 5.4. | 5.4.0 | 5.5.0-5.6.0|
 | <a name="3351941"></a> [3351941](#3351941) <a name="3351941"></a> <br /> | Cumulus Linux 5.4 package upgrade (<code>apt-upgrade</code>) does not support warm restart to complete the upgrade; performing an unsupported upgrade can result in unexpected or undesirable behavior, such as a traffic outage. | 5.4.0 | 5.5.0-5.6.0|
 | <a name="3350789"></a> [3350789](#3350789) <a name="3350789"></a> <br /> | NVUE deprecated the port split command options (2x10G, 2x25G, 2x40G, 2x50G, 2x100G, 2x200G, 4x10G, 4x25G, 4x50G, 4x100G, 8x50G) with no backwards compatibility. | 5.0.0-5.4.0 | 5.5.0-5.6.0|

content/cumulus-linux-54/rn.xml

@@ -385,13 +385,7 @@ To obtain the correct packages, install the {{tacplus-client}} package and its d
 </tr>
 <tr>
 <td>3362113</td>
-<td>If you restore an NVUE {{startup.yaml}} file after upgrade that includes breakout ports with QoS configuration or you run the {{nv config patch}} command to update a configuration with a {{yaml}} file that includes breakout ports with QoS configuration, the NVUE configuration fails to apply and subsequent attempts to run {{nv config apply}} fail with the following message: 
-
-cumulus@switch:~$ nv config apply
-Invalid config [rev_id: 11]
-  qos config is not supported on following invalid interface: swp1s0. Supported on swp and bond interface types.
-
-To work around this issue, run {{nv unset}} on the configured QoS settings, then apply the breakout port configuration before you configure QoS. Alternatively, you can remove the QoS configuration from the {{yaml}} file and patch it separately after applying the breakout configuration.</td>
+<td>If you restore an NVUE {{startup.yaml}} file after upgrade that includes breakout ports with QoS configuration or you run the {{nv config patch}} command to update a configuration with a {{yaml}} file that includes breakout ports with QoS configuration, the NVUE configuration fails to apply and subsequent attempts to run {{nv config apply}} fail with the message similar to {{Invalid config [rev_id: 11] qos config is not supported on following invalid interface: swp1s0. Supported on swp and bond interface types}}. To work around this issue, run {{nv unset}} on the configured QoS settings, then apply the breakout port configuration before you configure QoS. Alternatively, you can remove the QoS configuration from the {{yaml}} file and patch it separately after applying the breakout configuration.</td>
 <td>5.4.0-5.6.0</td>
 <td></td>
 </tr>