People run into problems on upgrades, for example:

 export http_proxy=http://172.xxx.xxx.xxx:8888/
 aptitude update && aptitude full-upgrade

This restarts pveproxy, and after that login was no longer possible.

Another way to reproduce the bug is:

 http_proxy=http://1.2.3.4:8888/ pveproxy --debug

The proxy call is done async, so the original connection can be
closed already. This just adds a reasonable warning message. We
can remove the message later if that turns out to work as expected.

timestamp don't have a real translation in french, and we regulary use english timestamp in the tech world
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>

Signed-off-by: Alexandre Derumier <aderumier@odiso.com>

more gettext cleanups

And use add_vm_to_pool/remove_vm_from_pool from PVE::AccessControl

Useful for clone API to restrict storage list.

Signed-off-by: Alexandre Derumier <aderumier@odiso.com>

hope this is correct.

Signed-off-by: Alexandre Derumier <aderumier@odiso.com>

Signed-off-by: Alexandre Derumier <aderumier@odiso.com>