2026-03-05 07:28:55.723 1 INFO magnum_cluster_api.proxy.manager [None req-d5efd416-b142-4da6-9338-81a7e6f50ed9 - - - - - -] Detected configuration change, reloading HAproxy
2026-03-05 07:28:55.724 1 INFO oslo.privsep.daemon [None req-d5efd416-b142-4da6-9338-81a7e6f50ed9 - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmp9jihgac1/privsep.sock']
2026-03-05 07:28:56.862 1 INFO oslo.privsep.daemon [None req-d5efd416-b142-4da6-9338-81a7e6f50ed9 - - - - - -] Spawned new privsep daemon via rootwrap
2026-03-05 07:28:56.766 13 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-03-05 07:28:56.772 13 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-03-05 07:28:56.779 13 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-03-05 07:28:56.779 13 INFO oslo.privsep.daemon [-] privsep daemon running as pid 13
2026-03-05 07:28:56.985 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (16) : New worker (18) forked
2026-03-05 07:28:56.986 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (16) : Loading success.
2026-03-05 07:29:01.879 13 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully