Strange Error/Warn message enabling kv secret engine

[bridany]

Describe the bug
Gor this message after succesfully enabled secret kv engine from UI:
Mar 10 09:53:44 vault-nodo1 vault[1268]: 2023-03-10T09:53:44.866+0100 [INFO] core: successful mount: namespace="" path=kvpu/ type=kv version=""
Mar 10 09:53:44 vault-nodo1 vault[1268]: 2023-03-10T09:53:44.967+0100 [WARN] secrets.kv.kv_67f85f42: Error sending event: error="event broker has not been started"

Is it only a Warming?

Environment:
3 Nodes Vault Enterprise Cluster behind Haproxy load balancer

• Vault Server Version :
• Vault v1.13.0+ent.hsm (d07983ca207de9fd561c24390ee2d84379739a32), built 2023-03-01T11:09:12Z (cgo)
• Server Operating System/Architecture:

Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-67-generic x86_64)
Linux vault-nodo1 5.15.0-67-generic #74-Ubuntu SMP Wed Feb 22 14:14:39 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
The Vault server is a vm running on on OracleVirtualBox Versione 7.0.6_rpmfusion r15 (running on Fedora 37 Host)

Vault server configuration file(s):

hcl
ui = true
disable_mlock = true
license_path = "/etc/vault.d/vault.hclic"

storage "raft" {
    path = "/opt/vault/data"
    node_id = "vault-nodo1"
    retry_join {
     leader_tls_servername   = "vault-nodo1.xxx.it"
     leader_api_addr         = "https://xxx.it:8200"
   }
   retry_join {
     leader_tls_servername   = "vault-nodo2.xxx.it"
     leader_api_addr         = "https://vault-nodo2.xxx.it:8200"
   }
     retry_join {
     leader_tls_servername   = "vault-nodo3.xxx.it"
     leader_api_addr         = "https://vault-nodo3.xxx.it:8200"
   }
}

listener "tcp" {
   address = "vault-nodo1.xxx.it:8200"
   cluster_address = "vault-nodo1.xxx.it:8201"
  tls_cert_file = "/opt/vault/tls/vault-nodo1.xxx.it.pem"
  tls_key_file  = "/opt/vault/tls/vault-nodo1.xxx.it.key"
 # tls_disable_client_certs = true
  # tls_disable = true
}


cluster_addr  = "https://vault-nodo1.xxx.it:8201"
api_addr      = "https://vault.xxx.it"

[VioletHynes]

Hi there!

I can confirm that this is only a warning. This was made as part of a new feature added to Vault for 1.13: https://developer.hashicorp.com/vault/docs/concepts/events

I can see how this might be confusing, though, and I'll pass it along to the team that implemented the event system. Thanks for the feedback! There's nothing to worry about :)

Thanks,
Violet