Newer
■
■
■
■
■
■
■
■
■
■
Older
88 lines
|
2.179kb
| 1 |
# Thunderbolt Interfaces Not in Bridge After MTU Fix |
|
| 2 | ||
| 3 |
## Issue ID: ISSUE-2025-002 |
|
| 4 | ||
| 5 |
**Status:** closed |
|
| 6 |
**Priority:** high |
|
| 7 |
**Created:** 2025-10-30 |
|
| 8 |
**Updated:** 2025-10-30 |
|
| 9 |
**Assigned to:** unassigned |
|
| 10 | ||
| 11 |
--- |
|
| 12 | ||
| 13 |
## Summary |
|
| 14 | ||
| 15 |
After applying the MTU fix, thunderbolt interfaces are no longer members of the thunderbridge. |
|
| 16 | ||
| 17 |
--- |
|
| 18 | ||
| 19 |
## Description |
|
| 20 | ||
| 21 |
Following the deployment of the MTU persistence fix (post-up hooks in interfaces.d), the thunderbolt interfaces failed to join the thunderbridge after `systemctl restart networking`. This regression broke cluster connectivity via thunderbolt. |
|
| 22 | ||
| 23 |
--- |
|
| 24 | ||
| 25 |
## Environment |
|
| 26 | ||
| 27 |
- **Affected nodes:** baobab, ebony, tapia |
|
| 28 |
- **Component:** network (thunderbolt bridging) |
|
| 29 |
- **Version/software:** Proxmox VE 8.x, ifupdown2, systemd services |
|
| 30 | ||
| 31 |
--- |
|
| 32 | ||
| 33 |
## Steps to Reproduce |
|
| 34 | ||
| 35 |
1. Deploy MTU fix with post-up hooks in `/etc/network/interfaces.d/10-thunderbolt`. |
|
| 36 |
2. Run `systemctl restart networking`. |
|
| 37 |
3. Check `bridge link show` - thunderbolt interfaces not in thunderbridge. |
|
| 38 | ||
| 39 |
--- |
|
| 40 | ||
| 41 |
## Expected Behavior |
|
| 42 | ||
| 43 |
Thunderbolt interfaces should remain in thunderbridge with MTU 65520 after networking restart. |
|
| 44 | ||
| 45 |
--- |
|
| 46 | ||
| 47 |
## Actual Behavior |
|
| 48 | ||
| 49 |
Interfaces have correct MTU but are not added to the bridge, causing loss of cluster connectivity. |
|
| 50 | ||
| 51 |
--- |
|
| 52 | ||
| 53 |
## Logs/Evidence |
|
| 54 | ||
| 55 |
``` |
|
| 56 |
# After restart networking |
|
| 57 |
$ bridge link show |
|
| 58 |
(no thunderbolt interfaces listed) |
|
| 59 | ||
| 60 |
$ ip link show thunderbolt0 |
|
| 61 |
thunderbolt0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 ... |
|
| 62 |
``` |
|
| 63 | ||
| 64 |
--- |
|
| 65 | ||
| 66 |
## Investigation Notes |
|
| 67 | ||
| 68 |
- 2025-10-30: Root cause identified - ifupdown2 brings up interfaces but systemd enlist services don't re-trigger on networking restart. Defense-in-depth needed. |
|
| 69 |
- 2025-10-30: Added `post-up ip link set dev $IFACE master thunderbridge || true` to interfaces.d files. |
|
| 70 | ||
| 71 |
--- |
|
| 72 | ||
| 73 |
## Proposed Solution |
|
| 74 | ||
| 75 |
Add bridge membership to post-up hooks in `/etc/network/interfaces.d/10-thunderbolt` for all nodes. |
|
| 76 | ||
| 77 |
--- |
|
| 78 | ||
| 79 |
## Related Issues |
|
| 80 | ||
| 81 |
- ISSUE-2025-001 (MTU reset issue) |
|
| 82 | ||
| 83 |
--- |
|
| 84 | ||
| 85 |
## Changelog References |
|
| 86 | ||
| 87 |
- CHANGELOG entry: [2025-10-30] - Fixed bridge membership regression after MTU fix deployment.</content> |
|
| 88 |
<parameter name="filePath">/Users/bogdan/Documents/Workspaces/Xdev/Madagascar/thunderbolts/issues/ISSUE-2025-002.md |