applied, thanks!
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> Since this fixes an actual bug people are running into it makes sense to
> apply this until someone can investigate how the open ssh connections
> manage to affect other independent ssh connections or migration
> processes.
OK, I applied the patch and upload packages to pvetest.
__
Ideally we'd find the root cause which I suspect somewhere in qemu's
handling of the open connection.
But the current code is apparently wrong in that the finish_tunnel() can
be skipped as the related phase3-cleanup portion is skipped if phase 2
errored.
Also avoiding the duplicated finish-block
Looks fine as the API currently only recognizes 'iso' and 'vztmpl',
while 'backup' runs into a `raise_param_exc()`.
On Tue, Feb 02, 2016 at 11:43:24AM +0100, Dominik Csapak wrote:
> since we do not want to upload vzdump backup files (see bug #498),
> it is confusing to expose this option in the gu
if we do not close it, there is a change that the tunnel stays open and the
next migration will not work.
---
PVE/QemuMigrate.pm | 24
1 file changed, 16 insertions(+), 8 deletions(-)
diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
index 7ae3880..5da62eb 100644
---
The *.Audit parts are definitely fine.
Note that while Sys.Console shows the Console tab, the console api call
itself also has a hardcoded check for realm == 'pam' and spawns a login
prompt for non-root users, so Sys.Console alone might not be equivalent
after all.
So there's still the question wh
since we do not want to upload vzdump backup files (see bug #498),
it is confusing to expose this option in the gui, since currently
it can never succeed.
the correct way would probably allow it based on the users permissions
Signed-off-by: Dominik Csapak
---
www/manager/storage/ContentView.js
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
