Re: [pve-devel] [PATCH v2 common] fix #1942: workaround for 'quiet' option conflict

On 10/8/18 3:19 PM, David Limbeck wrote: > workaround for option 'quiet' in VZDump conflicting with > standard_output_options in RESTHandler.pm. this change is not limited to > 'quiet' but also allows other options to be overridden as long as their > type property matches. > > Signed-off-by: David

Re: [pve-devel] Issue with CLI, when tried to create backup job

On 10/8/18 2:58 PM, Eduard Ahmatgareev wrote: > Does anybody have idea how it possible to fix? > Hi, this problem was reported over other channels too and it seems it was forgotten to answer yours.. Anyway, a proposed fix is here: https://pve.proxmox.com/pipermail/pve-devel/2018-October/033992.ht

Re: [pve-devel] applied: [PATCH v4 pve-manager] API2 : Network : add network config reload

>>applied, and added a few cleanups on top. Thanks Dietmar ! >>Please can you try to solve those issues marked as 'clean me'? I'm not sure what is the best/cleanest way to read/write and parse /etc/network/interfaces ? - Mail original - De: "dietmar" À: "pve-devel" , "aderumier"

[pve-devel] [PATCH container] close #1940: added ability to specify escape sequence

added the ability to pass a user defined escape sequence to pct console command Signed-off-by: Tim Marx --- src/PVE/CLI/pct.pm | 17 - src/PVE/LXC.pm | 6 +++--- 2 files changed, 19 insertions(+), 4 deletions(-) diff --git a/src/PVE/CLI/pct.pm b/src/PVE/CLI/pct.pm index 629

[pve-devel] [PATCH v2 common] fix #1942: workaround for 'quiet' option conflict

workaround for option 'quiet' in VZDump conflicting with standard_output_options in RESTHandler.pm. this change is not limited to 'quiet' but also allows other options to be overridden as long as their type property matches. Signed-off-by: David Limbeck --- This workaround was proposed by Dietmar

Re: [pve-devel] Issue with CLI, when tried to create backup job

Does anybody have idea how it possible to fix? чт, 4 окт. 2018 г. в 13:53, Eduard Ahmatgareev : > Hi, > > I tried to create new backup job on: > > root@cluster-13-1:/usr/share/perl5/PVE# pveversion -v > proxmox-ve: 5.2-2 (running kernel: 4.15.18-4-pve) > pve-manager: 5.2-9 (running version: 5.2-

[pve-devel] applied: [PATCH v4 pve-manager] API2 : Network : add network config reload

applied, and added a few cleanups on top. Please can you try to solve those issues marked as 'clean me'? > On October 2, 2018 at 9:19 AM Alexandre Derumier wrote: > > > This add a new api to online reload networking configuration > with ifupdown2. > > This work with native ifupdown2 modules,

[pve-devel] applied: [PATCH qemu-server] qemu_img_convert : use "-l snapshot.name" instead -s for internal snapshot

applied, thanks On Sun, Oct 07, 2018 at 07:15:22PM +0200, Alexandre Derumier wrote: > qemu-img convert -s has been removed in qemu 3.0 > https://git.qemu.org/?p=qemu.git;a=commit;h=46e8d272baa0608adcfdbd8bc1d2312bea06da40 > > we should use qemu-img convert -l snapshot.name=, > introduced in qemu

Re: [pve-devel] [PATCH manager] fix #1942: workaround for vzdump conflicting 'quiet' parameter

Sent it too soon, does not work. On 10/8/18 11:46 AM, David Limbeck wrote: workaround for 'quiet' parameter conflicting with standard_output_parameters in PVE/RESTHandler.pm as proposed by Dietmar Signed-off-by: David Limbeck --- PVE/VZDump.pm | 2 ++ 1 file changed, 2 insertions(+) diff -

[pve-devel] [PATCH manager] fix #1942: workaround for vzdump conflicting 'quiet' parameter

workaround for 'quiet' parameter conflicting with standard_output_parameters in PVE/RESTHandler.pm as proposed by Dietmar Signed-off-by: David Limbeck --- PVE/VZDump.pm | 2 ++ 1 file changed, 2 insertions(+) diff --git a/PVE/VZDump.pm b/PVE/VZDump.pm index 7fc69f98..57d371af 100644 --- a/PVE/V