fix(fleet): make local self-update flow reliable end-to-end (#472)

The "Updating Sencho..." overlay used to dismiss prematurely while the
image pull was still running, after which the local node card would get
stuck in "updating" and eventually surface a generic "Timed Out" error
while the container remained on the old version.

Three root causes are addressed:

1. The image pull was synchronous (`execFileSync`), which blocked the
   Node event loop. The overlay's health probe saw the server come back
   the moment the pull finished and reloaded the page, even though the
   container had not restarted yet. The pull is now async via
   `promisify(execFile)`, so /api/health and /api/fleet/update-status
   keep serving throughout.

2. The overlay reloaded on the first 200 from /api/health regardless of
   whether the underlying process had actually restarted. /api/health
   now exposes the gateway boot timestamp, and the overlay captures it
   pre-update and only reloads when it observes a different value. A
   wasOffline-then-online fallback handles the case where the pre-update
   fetch failed.

3. Helper container spawn errors from `docker run` were silently
   discarded, so a failed compose recreate never surfaced anywhere.
   Errors are now captured into `lastUpdateError` via the execFile
   callback and surfaced through the existing /api/fleet/update-status
   error path.

A 3-minute early-fail heuristic on the local node block surfaces a clear
failure message when the helper fails silently, instead of waiting the
full 5-minute timeout for an unknown failure.
This commit is contained in:
Anso
2026-04-10 12:00:44 -04:00
committed by GitHub
parent c09673d8bb
commit 3d69746eee
5 changed files with 103 additions and 22 deletions
+18 -7
View File
@@ -1,7 +1,10 @@
import { execFileSync, execFile } from 'child_process';
import { promisify } from 'util';
import DockerController from './DockerController';
import { disableCapability } from './CapabilityRegistry';
const execFileAsync = promisify(execFile);
interface ComposeContext {
workingDir: string;
configFiles: string;
@@ -86,22 +89,22 @@ class SelfUpdateService {
this.lastUpdateError = null;
}
triggerUpdate(): void {
async triggerUpdate(): Promise<void> {
if (!this.composeContext) return;
const { workingDir, configFiles, serviceName, imageName } = this.composeContext;
const env = { ...process.env, PATH: process.env.PATH || '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' };
this.lastUpdateError = null;
// Step 1: Pull latest image directly (no compose file needed)
// Async pull: a sync execFileSync blocks the event loop, which lets the frontend
// overlay see a false "online" response between the pull finishing and the restart.
console.log(`[SelfUpdate] Pulling latest image: ${imageName}...`);
try {
execFileSync('docker', ['pull', imageName], {
await execFileAsync('docker', ['pull', imageName], {
env,
stdio: 'pipe',
timeout: 300_000, // 5 min max for pull
});
} catch (error) {
const stderr = (error as { stderr?: Buffer })?.stderr?.toString().trim();
const stderr = (error as { stderr?: Buffer | string })?.stderr?.toString().trim();
this.lastUpdateError = stderr || (error as Error).message;
console.error('[SelfUpdate] Pull failed:', this.lastUpdateError);
return;
@@ -126,8 +129,16 @@ class SelfUpdateService {
'-c', composeCmd,
];
execFile('docker', args, { env });
// Process will be killed by Docker during recreate; no code runs after this
// Capture spawn errors (bad image, missing socket, permission denied) so they
// land in lastUpdateError instead of vanishing silently.
execFile('docker', args, { env }, (err, _stdout, stderr) => {
if (err) {
const stderrText = stderr?.toString().trim();
this.lastUpdateError = stderrText || err.message || 'Helper container failed to spawn';
console.error('[SelfUpdate] Helper container spawn failed:', this.lastUpdateError);
}
});
// No code after this point is guaranteed to run: the helper recreates this container.
}
}