proposer-nodes not preferred over beacon-nodes?

[ladidan]

Description & Present Behaviour

Even though the VC specifies --proposer-nodes A - which is confirmed to be available - block publishing is executed by a non-proposer-node (B). Route: VC signs off header (received via mev-boost) delivered from node B -> relay initially publishes the block -> after block release, B tries to publish but libp2p WARN message pops up due to duplication. Meanwhile, A displays no logs indicating any effort to publish the block.

Version

Node A: teku/v23.5.0
Node B: lighthouse/4.2.0 (non-proposer-only + connected builder mev_boost)
VC: lighthouse/4.2.0 (--proposer-nodes A; --beacon-nodes B,A)

Expected Behaviour

Assuming the unhappy case that the relay was DoSed (and B potentially as well), I would have expected A to be the preferred publisher.