dev

hu-zhangyingfix(sandbox): clean stale resources

cefd017e创建于 8月9日历史提交

文件	最后提交记录	最后更新时间
manager.go	fix(sandbox): clean stale resources A killed daemon can leave VMM processes and sockets, virtiofs backends, network slots, and persisted sandbox records behind. These resources can conflict with CNI allocation and prevent the next warm pool from starting. Delay warm pool startup until SandboxManager recovers VMM, volume, and network resources. During startup, release stale boot layouts through an explicit recovery path before removing their persistent records. Keep normal Delete semantics scoped to sandboxes owned by the current Manager instance. Remove live sandboxes through the normal Delete path during graceful shutdown. Retry a network slot creation once after rollback so one-shot CNI residue can be cleared without changing background refill and exponential backoff. Assisted-by: Codex:GPT-5.6-sol Signed-off-by: hu-zhangying <huzhangying@huawei.com>	2 个月前
types.go	fix(sandbox): clean stale resources A killed daemon can leave VMM processes and sockets, virtiofs backends, network slots, and persisted sandbox records behind. These resources can conflict with CNI allocation and prevent the next warm pool from starting. Delay warm pool startup until SandboxManager recovers VMM, volume, and network resources. During startup, release stale boot layouts through an explicit recovery path before removing their persistent records. Keep normal Delete semantics scoped to sandboxes owned by the current Manager instance. Remove live sandboxes through the normal Delete path during graceful shutdown. Retry a network slot creation once after rollback so one-shot CNI residue can be cleared without changing background refill and exponential backoff. Assisted-by: Codex:GPT-5.6-sol Signed-off-by: hu-zhangying <huzhangying@huawei.com>	2 个月前
virtiofs.go	fix(sandbox): clean stale resources A killed daemon can leave VMM processes and sockets, virtiofs backends, network slots, and persisted sandbox records behind. These resources can conflict with CNI allocation and prevent the next warm pool from starting. Delay warm pool startup until SandboxManager recovers VMM, volume, and network resources. During startup, release stale boot layouts through an explicit recovery path before removing their persistent records. Keep normal Delete semantics scoped to sandboxes owned by the current Manager instance. Remove live sandboxes through the normal Delete path during graceful shutdown. Retry a network slot creation once after rollback so one-shot CNI residue can be cleared without changing background refill and exponential backoff. Assisted-by: Codex:GPT-5.6-sol Signed-off-by: hu-zhangying <huzhangying@huawei.com>	2 个月前