2026-03-09 16:18:45.469 1 INFO magnum_cluster_api.proxy.manager [None req-4faa50eb-08fe-4a9b-b3c4-4b665845ab8b - - - - - -] Detected configuration change, reloading HAproxy
2026-03-09 16:18:45.470 1 INFO oslo.privsep.daemon [None req-4faa50eb-08fe-4a9b-b3c4-4b665845ab8b - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmpq4dzkrri/privsep.sock']
2026-03-09 16:18:46.503 1 INFO oslo.privsep.daemon [None req-4faa50eb-08fe-4a9b-b3c4-4b665845ab8b - - - - - -] Spawned new privsep daemon via rootwrap
2026-03-09 16:18:46.425 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-03-09 16:18:46.431 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-03-09 16:18:46.435 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-03-09 16:18:46.435 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-03-09 16:18:46.621 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-03-09 16:18:46.622 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-03-09 16:18:51.524 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully