I have attached 3 screenshots from tn09 showing the issue. It is impossible to configure a lagg without setting failover group, which then requires vhid, which then requires IPs. As shown in screen desired configuration this can only be achieved by using legacy UI which does not have any IP configuration on it's screen to build a lagg. I am including "lagg configuration" to show the actually error as well as "vlan using lagg" to show what why I am not configure an IP address on the lagg. Finally you can see from "legacy UI link aggregation config" that this workflow never required IP info. If you wanted to configure networking for lagg0 you would do that after it's creation under network -> interfaces. I believe if we don't want to recreate this work flow and cause disruption we must be able to have an exemption for this configuration of lagg devices not to require failover settings. Another possiblity might be to only require this settings when critical for failover is checked.
Steps to reproduce:
Configure lagg with 2 member interfaces cxl0, and cxl. Try to only enter lagg name lagg0 and save. Do not check critical for failover.
The validation errors appear that failover settings are required as shown in screenshot.
Enable legacy UI for TrueNAS 11.3-U3.2 and releases below to setup vlan with lagg on HA platform. Fix will be targetted for 11.3-U4 after discussing with engineering since there is a workaround.