From e4ecf0ff0bf77ec10ad7322a77de55ebabcd14f5 Mon Sep 17 00:00:00 2001 From: Walter Boring Date: Thu, 27 Aug 2026 10:40:06 -0400 Subject: [PATCH] cinder: add --single-child to dumb-init for backup pods Without --single-child, dumb-init sends SIGTERM to the entire process group. The ProcessLauncher parent exits before backup children finish draining in-flight operations (e.g., backup restore), and the kernel SIGKILLs the remaining processes. With --single-child, dumb-init forwards SIGTERM only to the ProcessLauncher parent, which then forwards to each child and waits for all children to exit. This matches the cinder-volume VMware deployment (added in #11680) and is required for the graceful shutdown feature (sapcc/cinder#358). See also: sapcc/cinder#314 (Antelope testing) --- openstack/cinder/templates/backup_deployment.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/openstack/cinder/templates/backup_deployment.yaml b/openstack/cinder/templates/backup_deployment.yaml index 1ab310de87d..d198350bfe4 100644 --- a/openstack/cinder/templates/backup_deployment.yaml +++ b/openstack/cinder/templates/backup_deployment.yaml @@ -88,6 +88,7 @@ template: | - CHOWN command: - dumb-init + - --single-child - cinder-backup env: {{- if .Values.sentry.enabled }}