2026-03-02 02:58:54.843 1 INFO magnum_cluster_api.proxy.manager [None req-eb75084d-15db-4f1a-8df6-16edef0717fe - - - - - -] Detected configuration change, reloading HAproxy
2026-03-02 02:58:54.844 1 INFO oslo.privsep.daemon [None req-eb75084d-15db-4f1a-8df6-16edef0717fe - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmphc24r8vy/privsep.sock']
2026-03-02 02:58:55.896 1 INFO oslo.privsep.daemon [None req-eb75084d-15db-4f1a-8df6-16edef0717fe - - - - - -] Spawned new privsep daemon via rootwrap
2026-03-02 02:58:55.802 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-03-02 02:58:55.809 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-03-02 02:58:55.813 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-03-02 02:58:55.813 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-03-02 02:58:56.023 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-03-02 02:58:56.027 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-03-02 02:59:00.919 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully