2026-10-27 00:43:51.034 1 INFO magnum_cluster_api.proxy.manager [None req-196d3414-9a4b-4ff6-9e39-eede2d82a6d8 - - - - - -] Detected configuration change, reloading HAproxy
2026-10-27 00:43:51.035 1 INFO oslo.privsep.daemon [None req-196d3414-9a4b-4ff6-9e39-eede2d82a6d8 - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmptaa6chzo/privsep.sock']
2026-10-27 00:43:52.067 1 INFO oslo.privsep.daemon [None req-196d3414-9a4b-4ff6-9e39-eede2d82a6d8 - - - - - -] Spawned new privsep daemon via rootwrap
2026-10-27 00:43:52.001 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-10-27 00:43:52.011 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-10-27 00:43:52.015 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-10-27 00:43:52.015 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-10-27 00:43:52.204 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-10-27 00:43:52.205 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-10-27 00:43:57.089 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully