2026-03-05 07:55:19.001 1 INFO magnum_cluster_api.proxy.manager [None req-fa0194ba-9676-47ed-882e-bf37bd5b5577 - - - - - -] Detected configuration change, reloading HAproxy
2026-03-05 07:55:19.002 1 INFO oslo.privsep.daemon [None req-fa0194ba-9676-47ed-882e-bf37bd5b5577 - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmpu_pp130n/privsep.sock']
2026-03-05 07:55:20.088 1 INFO oslo.privsep.daemon [None req-fa0194ba-9676-47ed-882e-bf37bd5b5577 - - - - - -] Spawned new privsep daemon via rootwrap
2026-03-05 07:55:19.996 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-03-05 07:55:20.002 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-03-05 07:55:20.006 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-03-05 07:55:20.007 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-03-05 07:55:20.207 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-03-05 07:55:20.207 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-03-05 07:55:25.105 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully