due to a timing race condition, it can happen that we try to increase
the 401 count before resetting it (which happens after the first
ticket api call). Since `undefined + ` === NaN, our later check for
`> 5` never triggers and we don't show the login mask, but an empty
window.
To fix this, initia
--- Begin Message ---
>
Hi,
> Also when changing lun size would have been grown on the storage
> side,
> it would be handy to have a button in pve web gui to "refresh" the
> disk in the vm. The new size should be reflected in the hardware
> details of the vm. And the qemu prozess should be infor
When creating a new network device from the UI and leaving the MTU
field empty, it defaults to 1500. This is inconvenient in cases where
the MTU of the bridge is not 1500 and lead to some confusion of users
[1]. Containers already inherit the bridge MTU when the field is left
empty, so align the be
superseded by v2:
https://lore.proxmox.com/pve-devel/20250417104855.144882-1-s.hanre...@proxmox.com/T
On 4/17/25 11:59, Stefan Hanreich wrote:
> When creating a new network device from the UI and leaving the MTU
> field empty, the field hints that this means that the MTU is inherited
> from the br
The default behavior changed from setting 1500 MTU to inheriting the
bridge MTU, if the MTU key for network devices is unset.
Signed-off-by: Stefan Hanreich
---
qm.adoc | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/qm.adoc b/qm.adoc
index 44e2436..29cb26c 100644
---
Leaving the MTU field unset now defaults to the bridge MTU, rather
than 1500. Reflect this change by indicating the new behavior in the
emptyText of the MTU field. While we're at it, add a gettext call so
it can be translated. I've taken the same text as from the container
dialogue, so it should al
The current default behavior for VirtIO network devices is to default to 1500
MTU, unless otherwise specified. This is inconvenient in cases where the MTU is
not the default value (e.g. for VXLAN VNets or bridges with jumbo frames).
Containers already inherit the MTU of the bridge, if not set, so c
When creating a new network device from the UI and leaving the MTU
field empty, the field hints that this means that the MTU is inherited
from the bridge. Since leaving the field empty omits the key from the
network device configuration, we need to inherit from the bridge MTU
when this key is missi
--- Begin Message ---
Citing https://ldapwiki.com/wiki/Wiki.jsp?page=PosixGroup
2307Bis says:
"Group members may either be login names (values of memberUid) or Distinguished
Names (values of uniqueMember). In the uniqueMember, the Distinguished Names
must be mapped to one or more login names by
