In an a4x2 run, I had a cluster come all the way up, except for a single nexus zone. Attached is the log from the sled agent responsible for launching the missing nexus zone.
The reason for the zone not coming up is sled-agent observing an uninitialized xde underlay state.
22:04:26.535Z WARN SledAgent (ServiceManager): Zone failed to start
file = sled-agent/src/services.rs:2998
zone = oxz_nexus_7ed9c5a4-18c2-4704-bd61-a1c12ffdbfe0
22:04:26.536Z INFO SledAgent (dropshot (SledAgent)): request completed
error_message_external = Internal Server Error
error_message_internal = Failed to initialize zones: [("oxz_nexus_7ed9c5a4-18c2-4704-bd61-a1c12ffdbfe0", ServicePortCreation { service: "nexus", err: Opte(CommandError(CreateXde, System { errno: 22, msg: "underlay not initialized" })) })]
However, earlier in the log file, sled agent appears to initialize the underlay.
2024-03-22 21:35:23.933Z INFO SledAgent/1376 on g3: using '[AddrObject { interface: "vioif1", name: "ll
" }, AddrObject { interface: "vioif2", name: "ll" }]' as data links for xde driver
file = illumos-utils/src/opte/illumos.rs:90
sled_id = 79f20df6-259c-4167-90ae-d840d6d84041
sled-agent-no-nexus.log
In an a4x2 run, I had a cluster come all the way up, except for a single nexus zone. Attached is the log from the sled agent responsible for launching the missing nexus zone.
The reason for the zone not coming up is sled-agent observing an uninitialized xde underlay state.
However, earlier in the log file, sled agent appears to initialize the underlay.
sled-agent-no-nexus.log