Unfortunately not. The error occurred immediately after the update from 2.3.0p19 to 2.3.0p30 – simultaneously on two Proxmox servers – a two-node cluster with quorum – the other three clusters (all with three or more nodes, thus without an additional quorum) do not have this error.