2026-03-03 18:38:40.762 1 INFO magnum_cluster_api.proxy.manager [None req-2c02d243-e721-46d5-a911-f0e70116d407 - - - - - -] Detected configuration change, reloading HAproxy
2026-03-03 18:38:40.763 1 INFO oslo.privsep.daemon [None req-2c02d243-e721-46d5-a911-f0e70116d407 - - - - - -] Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', 'magnum_cluster_api.privsep.haproxy_pctxt', '--privsep_sock_path', '/tmp/tmp4biw3a9k/privsep.sock']
2026-03-03 18:38:41.829 1 INFO oslo.privsep.daemon [None req-2c02d243-e721-46d5-a911-f0e70116d407 - - - - - -] Spawned new privsep daemon via rootwrap
2026-03-03 18:38:41.742 12 INFO oslo.privsep.daemon [-] privsep daemon starting
2026-03-03 18:38:41.749 12 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0
2026-03-03 18:38:41.752 12 INFO oslo.privsep.daemon [-] privsep process running with capabilities (eff/prm/inh): CAP_NET_ADMIN/CAP_NET_ADMIN/none
2026-03-03 18:38:41.753 12 INFO oslo.privsep.daemon [-] privsep daemon running as pid 12
2026-03-03 18:38:41.964 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : New worker (17) forked
2026-03-03 18:38:41.965 1 WARNING oslo.privsep.daemon [-] privsep log: [NOTICE]   (15) : Loading success.
2026-03-03 18:38:46.844 12 INFO magnum_cluster_api.privsep.haproxy [-] HAproxy started successfully