Open jgallagher opened 1 year ago
I'm not sure I would move straight to a retry, if we're not sure why this is happening. It seems like there could be a race of some kind, or we're not correctly waiting for a pool import or dataset mount to complete? I suspect that could be bad if sled agent is removing old things and that's racing with zoneadm creating new ones?
While cold-booting madrid, the sled-agent on the scrimlet bounced twice during startup. The first bounce is covered by #3789 and #3790. The error message on the second bounce was:
Searching back for that dataset UUID, it looks like sled-agent found it:
so it isn't clearly why
zoneadm
would have failed. After smf restarted sled-agent, it came up successfully the third time, so it seems likely that adding retries around service startup (#3790) will address this too.The full log from this sled-agent is at
/net/catacomb/data/staff/core/madrid/omicron-3789
.