2026-03-03 20:56:50.290 1 INFO magnum_cluster_api.proxy.manager [None req-955aa464-296c-4788-b841-ab8ebd850454 - - - - - -] Detected configuration change, reloading HAproxy
2026-03-03 20:56:50.291 1 INFO oslo.privsep.daemon [None req-955aa464-296c-4788-b841-ab8ebd850454 - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmpji9y2_hd/privsep.sock']
2026-03-03 20:56:51.325 1 INFO oslo.privsep.daemon [None req-955aa464-296c-4788-b841-ab8ebd850454 - - - - - -] Spawned new privsep daemon via rootwrap
2026-03-03 20:56:51.232 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-03-03 20:56:51.238 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-03-03 20:56:51.240 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-03-03 20:56:51.240 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-03-03 20:56:51.433 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-03-03 20:56:51.434 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-03-03 20:56:56.340 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully