2026-03-11 21:18:04.919 1 INFO magnum_cluster_api.proxy.manager [None req-ef6dd502-d8c3-47d0-8749-7e60b8c17cba - - - - - -] Detected configuration change, reloading HAproxy
2026-03-11 21:18:04.920 1 INFO oslo.privsep.daemon [None req-ef6dd502-d8c3-47d0-8749-7e60b8c17cba - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmp_auyu2h4/privsep.sock']
2026-03-11 21:18:05.970 1 INFO oslo.privsep.daemon [None req-ef6dd502-d8c3-47d0-8749-7e60b8c17cba - - - - - -] Spawned new privsep daemon via rootwrap
2026-03-11 21:18:05.890 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-03-11 21:18:05.896 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-03-11 21:18:05.900 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-03-11 21:18:05.900 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-03-11 21:18:06.086 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-03-11 21:18:06.086 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-03-11 21:18:10.988 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully