2026-03-18 10:46:05.631 1 INFO magnum_cluster_api.proxy.manager [None req-392f79dd-fd1a-4cfe-9434-191b5aaa26fe - - - - - -] Detected configuration change, reloading HAproxy
2026-03-18 10:46:05.633 1 INFO oslo.privsep.daemon [None req-392f79dd-fd1a-4cfe-9434-191b5aaa26fe - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmp6_shm5l6/privsep.sock']
2026-03-18 10:46:06.682 1 INFO oslo.privsep.daemon [None req-392f79dd-fd1a-4cfe-9434-191b5aaa26fe - - - - - -] Spawned new privsep daemon via rootwrap
2026-03-18 10:46:06.603 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-03-18 10:46:06.610 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-03-18 10:46:06.613 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-03-18 10:46:06.613 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-03-18 10:46:06.817 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-03-18 10:46:06.818 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-03-18 10:46:11.698 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully