2026-05-04 20:20:45.367 1 INFO magnum_cluster_api.proxy.manager [None req-2bc5603d-8c89-417e-bd58-878af036ee72 - - - - - -] Detected configuration change, reloading HAproxy
2026-05-04 20:20:45.368 1 INFO oslo.privsep.daemon [None req-2bc5603d-8c89-417e-bd58-878af036ee72 - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmpl7jnqvwq/privsep.sock']
2026-05-04 20:20:46.427 1 INFO oslo.privsep.daemon [None req-2bc5603d-8c89-417e-bd58-878af036ee72 - - - - - -] Spawned new privsep daemon via rootwrap
2026-05-04 20:20:46.348 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-05-04 20:20:46.353 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-05-04 20:20:46.357 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-05-04 20:20:46.357 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-05-04 20:20:46.538 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-05-04 20:20:46.538 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-05-04 20:20:51.444 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully