2026-04-03 03:27:32.189 1 INFO magnum_cluster_api.proxy.manager [None req-241c6678-4cf8-4ec8-844f-e37153f159d0 - - - - - -] Detected configuration change, reloading HAproxy
2026-04-03 03:27:32.190 1 INFO oslo.privsep.daemon [None req-241c6678-4cf8-4ec8-844f-e37153f159d0 - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmpljtyzkkw/privsep.sock']
2026-04-03 03:27:33.303 1 INFO oslo.privsep.daemon [None req-241c6678-4cf8-4ec8-844f-e37153f159d0 - - - - - -] Spawned new privsep daemon via rootwrap
2026-04-03 03:27:33.213 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-04-03 03:27:33.220 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-04-03 03:27:33.223 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-04-03 03:27:33.224 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-04-03 03:27:33.419 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-04-03 03:27:33.420 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-04-03 03:27:38.317 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully