Skip to content

Commit db683e3

Browse files
mergify[bot]mergify[bot]
authored
Merge pull request #3019 from CumulusNetworks/create-pull-request/patch
Changes by create-pull-request action
2 parents 0738f3c + 6330efa commit db683e3

File tree

14 files changed

+2212
-384
lines changed

14 files changed

+2212
-384
lines changed

‎content/cumulus-linux-37/Whats-New/rn.md‎

Lines changed: 9 additions & 9 deletions
Large diffs are not rendered by default.

‎content/cumulus-linux-37/rn.xml‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -428,7 +428,7 @@ $ cat /etc/network/ifupdown2/policy.d/vxlan.json
428428
<tr>
429429
<td>2648658</td>
430430
<td>If you try to use more than one percent of {{max-ecmp-nexthops}}, you get an error indicating a failure.</td>
431-
<td>3.7.15-4.3.3</td>
431+
<td>3.7.15-4.3.4</td>
432432
<td>4.4.0-4.4.5</td>
433433
</tr>
434434
<tr>
@@ -796,7 +796,7 @@ If you flap the link with the {{ip link set vni10100 down; ip link set vni10100
796796
<tr>
797797
<td>2549371</td>
798798
<td>When Optimized Multicast Flooding (OMF) is enabled with the {{bridge.optimized_mcast_flood = TRUE}} setting in the {{/etc/cumulus/switchd.conf}} file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.</td>
799-
<td>3.7.11-4.3.3</td>
799+
<td>3.7.11-4.3.4</td>
800800
<td>4.4.0-4.4.5</td>
801801
</tr>
802802
<tr>
@@ -2503,7 +2503,7 @@ sudo systemctl restart clagd.service</td>
25032503
<tr>
25042504
<td>2648658</td>
25052505
<td>If you try to use more than one percent of {{max-ecmp-nexthops}}, you get an error indicating a failure.</td>
2506-
<td>3.7.15-4.3.3</td>
2506+
<td>3.7.15-4.3.4</td>
25072507
<td>4.4.0-4.4.5</td>
25082508
</tr>
25092509
<tr>
@@ -2889,7 +2889,7 @@ If you flap the link with the {{ip link set vni10100 down; ip link set vni10100
28892889
<tr>
28902890
<td>2549371</td>
28912891
<td>When Optimized Multicast Flooding (OMF) is enabled with the {{bridge.optimized_mcast_flood = TRUE}} setting in the {{/etc/cumulus/switchd.conf}} file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.</td>
2892-
<td>3.7.11-4.3.3</td>
2892+
<td>3.7.11-4.3.4</td>
28932893
<td>4.4.0-4.4.5</td>
28942894
</tr>
28952895
<tr>
@@ -4697,7 +4697,7 @@ If you flap the link with the {{ip link set vni10100 down; ip link set vni10100
46974697
<tr>
46984698
<td>2549371</td>
46994699
<td>When Optimized Multicast Flooding (OMF) is enabled with the {{bridge.optimized_mcast_flood = TRUE}} setting in the {{/etc/cumulus/switchd.conf}} file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.</td>
4700-
<td>3.7.11-4.3.3</td>
4700+
<td>3.7.11-4.3.4</td>
47014701
<td>4.4.0-4.4.5</td>
47024702
</tr>
47034703
<tr>
@@ -6373,7 +6373,7 @@ If you flap the link with the {{ip link set vni10100 down; ip link set vni10100
63736373
<tr>
63746374
<td>2549371</td>
63756375
<td>When Optimized Multicast Flooding (OMF) is enabled with the {{bridge.optimized_mcast_flood = TRUE}} setting in the {{/etc/cumulus/switchd.conf}} file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.</td>
6376-
<td>3.7.11-4.3.3</td>
6376+
<td>3.7.11-4.3.4</td>
63776377
<td>4.4.0-4.4.5</td>
63786378
</tr>
63796379
<tr>
@@ -8463,7 +8463,7 @@ asic-monitor[7389]: File "/usr/lib/python2.7/dist-packages/cumulus/asic_monitor.
84638463
<tr>
84648464
<td>2549371</td>
84658465
<td>When Optimized Multicast Flooding (OMF) is enabled with the {{bridge.optimized_mcast_flood = TRUE}} setting in the {{/etc/cumulus/switchd.conf}} file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.</td>
8466-
<td>3.7.11-4.3.3</td>
8466+
<td>3.7.11-4.3.4</td>
84678467
<td>4.4.0-4.4.5</td>
84688468
</tr>
84698469
<tr>
@@ -10511,7 +10511,7 @@ To work around this issue, revert the configuration change.</td>
1051110511
<tr>
1051210512
<td>2549371</td>
1051310513
<td>When Optimized Multicast Flooding (OMF) is enabled with the {{bridge.optimized_mcast_flood = TRUE}} setting in the {{/etc/cumulus/switchd.conf}} file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.</td>
10514-
<td>3.7.11-4.3.3</td>
10514+
<td>3.7.11-4.3.4</td>
1051510515
<td>4.4.0-4.4.5</td>
1051610516
</tr>
1051710517
<tr>
@@ -12151,7 +12151,7 @@ To work around this issue, revert the configuration change.</td>
1215112151
<tr>
1215212152
<td>2549371</td>
1215312153
<td>When Optimized Multicast Flooding (OMF) is enabled with the {{bridge.optimized_mcast_flood = TRUE}} setting in the {{/etc/cumulus/switchd.conf}} file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.</td>
12154-
<td>3.7.11-4.3.3</td>
12154+
<td>3.7.11-4.3.4</td>
1215512155
<td>4.4.0-4.4.5</td>
1215612156
</tr>
1215712157
<tr>

‎content/cumulus-linux-40/Whats-New/rn.md‎

Lines changed: 12 additions & 12 deletions
Large diffs are not rendered by default.

‎content/cumulus-linux-40/rn.xml‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -234,19 +234,19 @@ cumulus@leaf01:~$ nv set vrf default router ospf area 0 network 10.10.10.1/32
234234
<tr>
235235
<td>2648658</td>
236236
<td>If you try to use more than one percent of {{max-ecmp-nexthops}}, you get an error indicating a failure.</td>
237-
<td>3.7.15-4.3.3</td>
237+
<td>3.7.15-4.3.4</td>
238238
<td>4.4.0-4.4.5</td>
239239
</tr>
240240
<tr>
241241
<td>2556764</td>
242242
<td>In a configuration with both traditional and VLAN-aware bridges, the VLAN membership check on a VLAN-aware bridge does not drop PVST BPBUs that come from a traditional bridge.</td>
243-
<td>3.7.14-3.7.14.2, 4.0.0-4.3.3</td>
243+
<td>3.7.14-3.7.14.2, 4.0.0-4.3.4</td>
244244
<td>3.7.15-3.7.16, 4.4.0-4.4.5</td>
245245
</tr>
246246
<tr>
247247
<td>2556500</td>
248248
<td>Cumulus Linux does not support bond members at 200G or greater.</td>
249-
<td>4.0.0-4.3.3</td>
249+
<td>4.0.0-4.3.4</td>
250250
<td>4.4.0-4.4.5</td>
251251
</tr>
252252
<tr>
@@ -600,7 +600,7 @@ To work around this issue, either do not set {{acl.non_atomic_update_mode = TRUE
600600
<tr>
601601
<td>2550601</td>
602602
<td>The received PVST BPDU for a VLAN is flooded even though the ingress port doesn't have the VLAN tagged.</td>
603-
<td>3.7.8-3.7.14.2, 4.0.0-4.3.3</td>
603+
<td>3.7.8-3.7.14.2, 4.0.0-4.3.4</td>
604604
<td>3.7.15-3.7.16, 4.4.0-4.4.5</td>
605605
</tr>
606606
<tr>
@@ -718,7 +718,7 @@ To work around this issue, when you manually configure the {{rd}} or {{route-tar
718718
<tr>
719719
<td>2549371</td>
720720
<td>When Optimized Multicast Flooding (OMF) is enabled with the {{bridge.optimized_mcast_flood = TRUE}} setting in the {{/etc/cumulus/switchd.conf}} file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.</td>
721-
<td>3.7.11-4.3.3</td>
721+
<td>3.7.11-4.3.4</td>
722722
<td>4.4.0-4.4.5</td>
723723
</tr>
724724
<tr>
@@ -1511,7 +1511,7 @@ To avoid this issue, wait 15 seconds before insertion and before removal of the
15111511
<tr>
15121512
<td>2545239</td>
15131513
<td>On the Mellanox switch with the Spectrum-2 ASIC, Precision Time Protocol (PTP) is not currently supported. </td>
1514-
<td>4.0.0-4.3.3</td>
1514+
<td>4.0.0-4.3.4</td>
15151515
<td>4.4.0-4.4.5</td>
15161516
</tr>
15171517
<tr>
@@ -2604,19 +2604,19 @@ cumulus@leaf01:~$ nv set vrf default router ospf area 0 network 10.10.10.1/32
26042604
<tr>
26052605
<td>2648658</td>
26062606
<td>If you try to use more than one percent of {{max-ecmp-nexthops}}, you get an error indicating a failure.</td>
2607-
<td>3.7.15-4.3.3</td>
2607+
<td>3.7.15-4.3.4</td>
26082608
<td>4.4.0-4.4.5</td>
26092609
</tr>
26102610
<tr>
26112611
<td>2556764</td>
26122612
<td>In a configuration with both traditional and VLAN-aware bridges, the VLAN membership check on a VLAN-aware bridge does not drop PVST BPBUs that come from a traditional bridge.</td>
2613-
<td>3.7.14-3.7.14.2, 4.0.0-4.3.3</td>
2613+
<td>3.7.14-3.7.14.2, 4.0.0-4.3.4</td>
26142614
<td>3.7.15-3.7.16, 4.4.0-4.4.5</td>
26152615
</tr>
26162616
<tr>
26172617
<td>2556500</td>
26182618
<td>Cumulus Linux does not support bond members at 200G or greater.</td>
2619-
<td>4.0.0-4.3.3</td>
2619+
<td>4.0.0-4.3.4</td>
26202620
<td>4.4.0-4.4.5</td>
26212621
</tr>
26222622
<tr>
@@ -2970,7 +2970,7 @@ To work around this issue, either do not set {{acl.non_atomic_update_mode = TRUE
29702970
<tr>
29712971
<td>2550601</td>
29722972
<td>The received PVST BPDU for a VLAN is flooded even though the ingress port doesn't have the VLAN tagged.</td>
2973-
<td>3.7.8-3.7.14.2, 4.0.0-4.3.3</td>
2973+
<td>3.7.8-3.7.14.2, 4.0.0-4.3.4</td>
29742974
<td>3.7.15-3.7.16, 4.4.0-4.4.5</td>
29752975
</tr>
29762976
<tr>
@@ -3088,7 +3088,7 @@ To work around this issue, when you manually configure the {{rd}} or {{route-tar
30883088
<tr>
30893089
<td>2549371</td>
30903090
<td>When Optimized Multicast Flooding (OMF) is enabled with the {{bridge.optimized_mcast_flood = TRUE}} setting in the {{/etc/cumulus/switchd.conf}} file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.</td>
3091-
<td>3.7.11-4.3.3</td>
3091+
<td>3.7.11-4.3.4</td>
30923092
<td>4.4.0-4.4.5</td>
30933093
</tr>
30943094
<tr>
@@ -3881,7 +3881,7 @@ To avoid this issue, wait 15 seconds before insertion and before removal of the
38813881
<tr>
38823882
<td>2545239</td>
38833883
<td>On the Mellanox switch with the Spectrum-2 ASIC, Precision Time Protocol (PTP) is not currently supported. </td>
3884-
<td>4.0.0-4.3.3</td>
3884+
<td>4.0.0-4.3.4</td>
38853885
<td>4.4.0-4.4.5</td>
38863886
</tr>
38873887
<tr>

0 commit comments

Comments
 (0)