2026-02-24 20:47:37.727 1 INFO magnum_cluster_api.proxy.manager [None req-2ad5dc67-5d17-4f91-a4dd-be21c43366d9 - - - - - -] Detected configuration change, reloading HAproxy
2026-02-24 20:47:37.728 1 INFO oslo.privsep.daemon [None req-2ad5dc67-5d17-4f91-a4dd-be21c43366d9 - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmp6eovdre2/privsep.sock']
2026-02-24 20:47:38.756 1 INFO oslo.privsep.daemon [None req-2ad5dc67-5d17-4f91-a4dd-be21c43366d9 - - - - - -] Spawned new privsep daemon via rootwrap
2026-02-24 20:47:38.678 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-02-24 20:47:38.684 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-02-24 20:47:38.688 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-02-24 20:47:38.688 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-02-24 20:47:38.872 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-02-24 20:47:38.873 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-02-24 20:47:43.771 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully