2026-03-02 19:47:13.634 1 INFO magnum_cluster_api.proxy.manager [None req-55e0cc46-d5e7-448f-a854-80bcf72cebac - - - - - -] Detected configuration change, reloading HAproxy
2026-03-02 19:47:13.635 1 INFO oslo.privsep.daemon [None req-55e0cc46-d5e7-448f-a854-80bcf72cebac - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmp04tm7cv3/privsep.sock']
2026-03-02 19:47:14.752 1 INFO oslo.privsep.daemon [None req-55e0cc46-d5e7-448f-a854-80bcf72cebac - - - - - -] Spawned new privsep daemon via rootwrap
2026-03-02 19:47:14.673 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-03-02 19:47:14.680 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-03-02 19:47:14.683 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-03-02 19:47:14.684 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-03-02 19:47:14.875 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-03-02 19:47:14.876 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-03-02 19:47:19.769 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully