2026-04-29 02:46:00.687 1 INFO magnum_cluster_api.proxy.manager [None req-6d39dbeb-6b99-4ba4-b55e-573ddad91234 - - - - - -] Detected configuration change, reloading HAproxy
2026-04-29 02:46:00.688 1 INFO oslo.privsep.daemon [None req-6d39dbeb-6b99-4ba4-b55e-573ddad91234 - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmp5pooamkg/privsep.sock']
2026-04-29 02:46:01.746 1 INFO oslo.privsep.daemon [None req-6d39dbeb-6b99-4ba4-b55e-573ddad91234 - - - - - -] Spawned new privsep daemon via rootwrap
2026-04-29 02:46:01.663 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-04-29 02:46:01.670 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-04-29 02:46:01.674 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-04-29 02:46:01.674 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-04-29 02:46:01.879 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-04-29 02:46:01.880 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-04-29 02:46:06.762 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully