Am 15.09.25 um 08:51 schrieb Hannes Laimer:
> On 12.09.25 18:36, Thomas Lamprecht wrote:
>> Am 12.09.25 um 12:17 schrieb Hannes Laimer:
>>> We showed this warning for setups with two nodes and a qdevice, but for
>>> setups like this this warning didn't make Sense. This checks if a
>>> qdevice is connected to the cluster before showing the 'not enough votes
>>> for reliable HA'-warning.
>>
>> Maybe it would be a bit more robust if we fleece that info in already in
>> the backend – but disclaimer: I did not just check, so you really need
>> to evaluate if it indeed makes sense or if applying this now as is might
>> be the better route forward.
>>
>
> I did consider that, but the `/cluster/config/nodes` endpoint seems to
> really only be intended for actual corosync nodes, it is also used like
> that. We could maybe add a `include-qdevice`-flag, but I think that
> would seem rather out-of-place
> ```
> {
> "name": "qClusterN1",
> "node": "qClusterN1",
> "nodeid": "1",
> "quorum_votes": "1",
> "ring0_addr": "192.168.55.44"
> },
> ```
> is what it currently returns, none of those fields except name(?) would
> really make sense for a qdevice.
True, if, that would better fit in a new status endpoint there,
but I see no hard need for creating such a endpoint just for
this check now.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
