@olivierlambert (first post, def won't be last though, break through being shy) Apologies in advance if wrong location. ;(
Heads up: What I observed, PIF status may show "Disconnected" on healthy OVS LACP bonds
Wanted to flag something in case it saves someone a debugging detour — after upgrading from an older XOA build (472 commits behind) (yes I know) to current master, the network view showed our eth2+eth3 bond's PIFs as "Disconnected" pool-wide, including individual PIFs on 2 of 3 hosts in the per-network detail panel.
Gave me a tense scare (client-facing subnet/vlan), so we went to CLI to get ground truth before assuming an outage (though obvious services working fine in that network).
* ovs-appctl bond/show on all three hosts: lacp_status: negotiated, both members enabled/may_enable: true, active traffic balanced across both interfaces (balance-tcp).
* ethtool confirms link detected, 10Gb/s full duplex, both physical NICs.
* XAPI's own PIF object reports currently-attached: true for the bond master.
So the bond itself is fully healthy — this looks like it's specific to how the PIF status is being surfaced in XO 6, not an actual connectivity problem or a stale XAPI record. Sharing in case it's useful data toward the read-only-mode maturity you mentioned in the announcement.
XO commit: 5.208.3 (rebuilt from source today)
All nodes(3) within the last week:
XCP-ng version: 8.3.0 (xapi 26.1.16, network_backend: openvswitch)