2026-04-07 16:00:58.835 1 INFO magnum_cluster_api.proxy.manager [None req-989372db-9e26-412e-afa1-2b5fc6ae25b3 - - - - - -] Detected configuration change, reloading HAproxy
2026-04-07 16:00:58.836 1 INFO oslo.privsep.daemon [None req-989372db-9e26-412e-afa1-2b5fc6ae25b3 - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmp3p2rwcq1/privsep.sock']
2026-04-07 16:00:59.851 1 INFO oslo.privsep.daemon [None req-989372db-9e26-412e-afa1-2b5fc6ae25b3 - - - - - -] Spawned new privsep daemon via rootwrap
2026-04-07 16:00:59.780 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-04-07 16:00:59.784 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-04-07 16:00:59.787 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-04-07 16:00:59.787 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-04-07 16:00:59.968 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-04-07 16:00:59.968 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-04-07 16:01:04.866 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully