prevent empty critical bond interfaces on HA
Description
Problem/Justification
None
Impact
None
Activity
Show:
Bug Clerk November 2, 2024 at 1:27 PM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.
Bug Clerk November 2, 2024 at 1:24 PM
24.10.1 PR: https://github.com/truenas/middleware/pull/14853
Bug Clerk November 2, 2024 at 1:24 PM
24.10.0.1 PR: https://github.com/truenas/middleware/pull/14852
Complete
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Caleb
CalebReporter
Bug Clerk
Bug ClerkLabels
Time remaining
0m
Components
Affects versions
Priority
MediumKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created November 2, 2024 at 12:55 PM
Updated November 5, 2024 at 9:03 PM
Resolved November 2, 2024 at 1:27 PM
25.04 PR: https://github.com/truenas/middleware/pull/14851
This was brought to my attention by support team because a particular customer had run into this scenario. We allow "empty" bond configurations because, most often times, the user will put vlans on top of it. However, some users will mark the bond interface as critical for failover and will NOT mark the child interfaces critical for failover. This paints the false impression that when the bond goes down, a failover event will be generated. This is not the case because we act upon network events for generating failover events. If the bond has no IP address, then it will not generate a failover event and because the child interface isn't marked critical for failover, a failover will not take place.