[pve-devel] [PATCH docs] pveum: switch OATH 2.0 to the correct OAuth 2.0; use pve not Proxmox

2025-02-27 Thread Shannon Sterz
this Signed-off-by: Shannon Sterz --- pveum.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pveum.adoc b/pveum.adoc index 81565ab..0cc267e 100644 --- a/pveum.adoc +++ b/pveum.adoc @@ -160,7 +160,7 @@ as an authentication protocol. OpenID Connect:: -OpenID Connec

Re: [pve-devel] [PATCH pve-http-server 1/1] close TLS gracefully to avoid unexpected EOF at client

2025-02-27 Thread Fabian Grünbichler
> Rob Rozestraten via pve-devel hat am 26.02.2025 > 23:51 CET geschrieben: Hi (and thanks for your patch)! A little bit of analysis of *why* this is needed and okay would be great to have here in the commit message ;) If I read the docs right, this could block (would that be an issue here?)

Re: [pve-devel] [PATCH docs] pveum: switch OATH 2.0 to the correct OAuth 2.0; use pve not Proxmox

2025-02-27 Thread Shannon Sterz
On Thu Feb 27, 2025 at 11:00 AM CET, Thomas Lamprecht wrote: > Am 27.02.25 um 10:42 schrieb Shannon Sterz: >> this > > this what? hm strange, sorry that seems to have gotten cut of: this switches the use of OATH 2.0 to the correct spelling of OAuth 2.0. it also makes it clear that the OpenID Con

Re: [pve-devel] [PATCH docs] pveum: switch OATH 2.0 to the correct OAuth 2.0; use pve not Proxmox

2025-02-27 Thread Thomas Lamprecht
Am 27.02.25 um 10:42 schrieb Shannon Sterz: > this this what? > > Signed-off-by: Shannon Sterz > --- > pveum.adoc | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/pveum.adoc b/pveum.adoc > index 81565ab..0cc267e 100644 > --- a/pveum.adoc > +++ b/pveum.adoc > @@ -16

Re: [pve-devel] [PATCH manager] pvestatd: improve broadcast of node version-info

2025-02-27 Thread Fabian Grünbichler
On February 27, 2025 9:59 am, Fiona Ebner wrote: > Am 26.02.25 um 17:02 schrieb Aaron Lauterer: >> >> >> On  2025-01-17  13:18, Fiona Ebner wrote: >>> Am 16.01.25 um 17:30 schrieb Aaron Lauterer: Until now, the pvestatd did broadcast the pve-manager version only once after startup of th

Re: [pve-devel] [PATCH manager] pvestatd: improve broadcast of node version-info

2025-02-27 Thread Fiona Ebner
Am 27.02.25 um 15:52 schrieb Fabian Grünbichler: > On February 27, 2025 9:59 am, Fiona Ebner wrote: >> Am 26.02.25 um 17:02 schrieb Aaron Lauterer: >>> >>> >>> On  2025-01-17  13:18, Fiona Ebner wrote: Am 16.01.25 um 17:30 schrieb Aaron Lauterer: > Until now, the pvestatd did broadcast the

Re: [pve-devel] [PATCH manager] pvestatd: improve broadcast of node version-info

2025-02-27 Thread Fabian Grünbichler
> Fiona Ebner hat am 27.02.2025 16:00 CET geschrieben: > > > Am 27.02.25 um 15:52 schrieb Fabian Grünbichler: > > On February 27, 2025 9:59 am, Fiona Ebner wrote: > >> Am 26.02.25 um 17:02 schrieb Aaron Lauterer: > >>> > >>> > >>> On  2025-01-17  13:18, Fiona Ebner wrote: > Am 16.01.25 um

Re: [pve-devel] [PATCH manager] pvestatd: improve broadcast of node version-info

2025-02-27 Thread Aaron Lauterer
sent a v2 https://lore.proxmox.com/pve-devel/20250227143356.1089350-1-a.laute...@proxmox.com/T/#u On 2025-01-16 17:30, Aaron Lauterer wrote: Until now, the pvestatd did broadcast the pve-manager version only once after startup of the service. But there are some situations, where the local pmx

[pve-devel] [PATCH manager v2] fix #5894: pvestatd: improve broadcast of node version-info

2025-02-27 Thread Aaron Lauterer
Until now, the pvestatd did broadcast the pve-manager version only once after startup of the service. But there are some situations, where the local pmxcfs (pve-cluster) restarts and loses that information. Basically everytime we restart the pmxcfs without restarting pvestatd too. For example, on

Re: [pve-devel] [PATCH manager] pvestatd: improve broadcast of node version-info

2025-02-27 Thread Aaron Lauterer
On 2025-01-16 17:50, Christian Ebner wrote: On 1/16/25 17:38, Aaron Lauterer wrote: On  2025-01-16  17:35, Christian Ebner wrote: On 1/16/25 17:30, Aaron Lauterer wrote: […] This will close issue 5894 I guess [0]? [0] https://bugzilla.proxmox.com/show_bug.cgi?id=5894 Specifically, th

[pve-devel] [PATCH qemu-server] hotplug pending: disallow deleting tpmstate and efidisk from configuration

2025-02-27 Thread Fiona Ebner
When the VM is running, after deleting the tpmstate from the configuration, the TPM drive will still be active, because it is used by swtpm and QEMU will still have the TPM socket. Also, a subsequent live migration will fail, because the commandline for the target instance does not match the one f

Re: [pve-devel] [PATCH manager] pvestatd: improve broadcast of node version-info

2025-02-27 Thread Fiona Ebner
Am 26.02.25 um 17:02 schrieb Aaron Lauterer: > > > On  2025-01-17  13:18, Fiona Ebner wrote: >> Am 16.01.25 um 17:30 schrieb Aaron Lauterer: >>> Until now, the pvestatd did broadcast the pve-manager version only once >>> after startup of the service. But there are some situations, where the >>> l

[pve-devel] [PATCH] dns: powerdns: correctly handle different records types (A / AAAA)

2025-02-27 Thread Matthieu Pignolet via pve-devel
--- Begin Message --- This fixes an issue with dual stacking, when using a zone with both a V4 and V6 subnet and the same dns suffix, pve-network will try to set both dns records (type A and ) in the same powerdns rrset, causing an api error, and effectively causing no forward dns records bei

Re: [pve-devel] [PATCH widget-toolkit v3 4/4] form: set enforceMaxLength on textareafield

2025-02-27 Thread Gabriel Goller
On 26.02.2025 18:59, Thomas Lamprecht wrote: Am 10.12.24 um 17:11 schrieb Gabriel Goller: This allows us to set `maxLength` on it. `enforceMaxLength` will force extjs to set the `maxLength` property on the underlying inputfield. isn't it enough to make the field invalid? It might not be a bi