Am 14.12.23 um 15:11 schrieb Lukas Wagner:
> The old backup job notification mails from before the notification
> system overhaul included the total time as well as the total size.
>
> The total size was missing from the new, template-based backup report,
> thus we add it back in this commit.
>
>
to avoid a failing null check and its error message. This confused
users since the activation was successful anyway.
Signed-off-by: Alexander Zeidler
---
v2:
* use "return" instead of "return undef"
* add commit message
v1: https://lists.proxmox.com/pipermail/pve-devel/2024-January/061280.html
On Wed, 2024-01-10 at 11:59 +0100, Alexander Zeidler wrote:
> On Wed, 2024-01-10 at 10:29 +0100, Thomas Lamprecht wrote:
> > any reason this is relevant you might want to add to the commit
> > message here?
> to avoid a failing null check and its error message. This confused
> users since the activ
When running `zfs mount -a`, prevent the exported datasets (with sharenfs)
to be truncated (unexported).
Adds tests to verify shares persist after mount -a
Signed-off-by: Stefan Lendl
---
This was merged upstream via https://github.com/openzfs/zfs/pull/15660
...do-not-truncate-shares-not-zfs-mo
Allow bridges to have any valid interface name
Repo: proxmox-widget-toolkit
Allow the web UI to accept bridge interfaces with any valid interface name,
rather than being limited to the arbitrary "vmbr" prefix.
Signed-off-by: Jillian Morgan
---
proxmox-widget-toolkit/src/Toolkit.js | 2 +-
1 fil
Allow bridges to have any valid interface name
The patches are 1-line each, but across two repositories:
proxmox-widget-toolkit (Toolkit.js)
pve-common (INotify.pm)
Jillian Morgan (2):
Allow bridges to have any valid interface name
Detect bridge interface by bridge_ports attribute
src/T
Detect bridge interface by bridge_ports attribute
Repo: pve-common
Similar to other interface types, we can detect a bridge by the presense of
it's bridge_ports attribute rather than solely relying on the "vmbr" ifname
prefix heuristic.
Signed-off-by: Jillian Morgan
---
pve-common/src/PVE/INoti
On Thu, 2024-01-25 at 16:28 +0800, YU Jincheng wrote:
> Accroding to RFC 8555:
>
> > The MAC key SHOULD be provided in base64url-encoded form...
>
> However, currently we are only decoding the MAC key as base64.
> This patch chooses the correct function to decode the user provided
> MAC key. This
Fix a bug that allows a device passthrough entry to be added to the
config despite the device path not pointing to a device. Previously,
adding an invalid device passthrough entry would throw an error, but the
entry would still be added to the config. This is fixed by moving the
respective checks f
This is a bug in pve-container. I sent a patch for it:
https://lists.proxmox.com/pipermail/pve-devel/2024-January/061513.html
On 26/01/2024 16:23, Fiona Ebner wrote:
- if I add /dev/doesnotexist I'll get an error but it'll still be added
to the configuration
Am 25.01.24 um 15:41 schrieb Fiona Ebner:
> In preparation to fix an issue for backup fleecing where discarding
> the source would lead to an assertion failure when the fleecing image
> has larger granularity than the backup target.
>
> Signed-off-by: Fiona Ebner
> ---
>
> Still need to wait on
to reflect current ZFS defaults.
Signed-off-by: Aaron Lauterer
---
unless I have missed it, we currently still show the old default as
placeholder
www/manager6/storage/ZFSPoolEdit.js | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www/manager6/storage/ZFSPoolEdit.js
b/www/m
Am 29.01.24 um 15:42 schrieb Aaron Lauterer:
> to reflect current ZFS defaults.
>
> Signed-off-by: Aaron Lauterer
> ---
> unless I have missed it, we currently still show the old default as
> placeholder
>
> www/manager6/storage/ZFSPoolEdit.js | 2 +-
> 1 file changed, 1 insertion(+), 1 deletio
Am 25.01.24 um 15:41 schrieb Fiona Ebner:
> Management for fleecing images is implemented here. If the fleecing
> option is set, for each disk (except EFI disk and TPM state) a new raw
> fleecing image is allocated on the configured fleecing storage (same
> storage as original disk by default). The
Am 25.01.24 um 15:41 schrieb Fiona Ebner:
> +storage => get_standard_option('pve-storage-id', {
> + description => "Use this storage to storage fleecing images. Default is
> to use the same "
> + ."storage as the VM disk itself.",
> + optional => 1,
> +}),
> +});
> +
LVM a
proxmox-perl-rs set's SSL_CERT_{DIR,FILE}, which can break ssl in
containers if their certificate store can't be found in the same spot.
This patch explicitly unsets those variables before starting the
container.
Signed-off-by: Folke Gleumes
---
Changes since v1:
* Add reevaluation notice for pve
The keep-env option allows the user to define if the current environment
should be kept when running 'pct enter/exec'. pct will now always set
'--keep-env' or '--discard-env' when calling lxc-attach to anticipate
the upcoming change in default behavior.
Signed-off-by: Folke Gleumes
---
This wasn'
17 matches
Mail list logo
