2026-05-10 04:53:45.075 1 INFO magnum_cluster_api.proxy.manager [None req-0224dfa4-60c5-49a4-8487-9527d19c5dea - - - - - -] Detected configuration change, reloading HAproxy
2026-05-10 04:53:45.076 1 INFO oslo.privsep.daemon [None req-0224dfa4-60c5-49a4-8487-9527d19c5dea - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmpyit94m9x/privsep.sock']
2026-05-10 04:53:46.292 1 INFO oslo.privsep.daemon [None req-0224dfa4-60c5-49a4-8487-9527d19c5dea - - - - - -] Spawned new privsep daemon via rootwrap
2026-05-10 04:53:46.212 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-05-10 04:53:46.218 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-05-10 04:53:46.222 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-05-10 04:53:46.222 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-05-10 04:53:46.433 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-05-10 04:53:46.434 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-05-10 04:53:51.303 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully