From: Petric Frank <pfrank@gmx.de>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Backup job requires email
Date: Fri, 26 Feb 2021 18:09:28 +0100 [thread overview]
Message-ID: <2485001.XQYqjrCR6X@main> (raw)
In-Reply-To: <e7389617-bfbd-ee7f-7f58-893bcf0b2bd7@proxmox.com>
Hello,
confirmed. Made an upgrade of the system a few minutes ago. Bug fixed.
Thanks.
regards
Petric
Am Donnerstag, 25. Februar 2021, 09:01:00 CET schrieb Fabian Ebner:
> Hi,
> yes, this was a regression and should be fixed with
> libpve-guest-common-perl >= 3.1-5 and libpve-common-perl >= 6.3-4 that
> are available in the no-subscription repository.
>
> Am 24.02.21 um 17:50 schrieb Petric Frank:
> > Hello,
> >
> > wanted to create an scheduled backup job via Datacenter -> Backup.
> >
> > In earlier versions on Proxmox you don't have to give a notification
> > eMail-
> > address. But now you have to enter one in the field "Send email to:". Also
> > the field "Email notification" only gives the options "Always" or "On
> > failure only", but not something like "None".
> >
> > Actually running Proxmox Virtual Environment 6.3-3
> >
> > Is this a bug in the web-gui ?
> >
> > Is there a command line tool to create the job ?
> >
> > Ok, i can create a cron entry ...
> >
> > kind regards
> >
> > Petric
> >
> > _______________________________________________
> > pve-user mailing list
> > pve-user@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2021-02-26 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 16:50 Petric Frank
2021-02-25 8:01 ` Fabian Ebner
2021-02-26 17:09 ` Petric Frank [this message]
2021-02-26 16:47 ` Petric Frank
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2485001.XQYqjrCR6X@main \
--to=pfrank@gmx.de \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.