From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES v3] fix #3903: remove vmid from jobs.cfg on destroy
Date: Mon, 14 Mar 2022 09:26:54 +0000 [thread overview]
Message-ID: <20220314092657.48696-1-h.laimer@proxmox.com> (raw)
... if 'purge'.
v3, based on Fabian Ebner's feedback:
- correctly handle 'exclude'
- move plugin specific stuff into the corresponding plugin(currently
just VZDump)
- add missing call to remove_job, when removing job
v2, based on Fabian Ebner's feedback:
- rewrote remove_vmid_from_jobs sub
- add missing 'use' statements
pve-manager:
Hannes Laimer (1):
fix #3903: jobs: add remove vmid from jobs helper
PVE/Jobs.pm | 21 ++++++++++++++++++++-
PVE/Jobs/Plugin.pm | 7 +++++++
PVE/Jobs/VZDump.pm | 13 +++++++++++++
3 files changed, 40 insertions(+), 1 deletion(-)
pve-container:
Hannes Laimer (1):
fix #3903: api2: remove vmid from jobs.cfg
src/PVE/API2/LXC.pm | 2 ++
1 file changed, 2 insertions(+)
qemu-server:
Hannes Laimer (1):
fix #3903: api2: remove vmid from jobs.cfg
PVE/API2/Qemu.pm | 2 ++
1 file changed, 2 insertions(+)
--
2.30.2
next reply other threads:[~2022-03-14 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 9:26 Hannes Laimer [this message]
2022-03-14 9:26 ` [pve-devel] [PATCH pve-manager v3 1/3] fix #3903: jobs: add remove vmid from jobs helper Hannes Laimer
2022-03-14 10:00 ` Fabian Ebner
2022-03-14 10:18 ` Fabian Ebner
2022-03-15 10:52 ` [pve-devel] [PATCH pve-manager v4 " Hannes Laimer
2022-03-14 9:26 ` [pve-devel] [PATCH pve-container v3 2/3] fix #3903: api2: remove vmid from jobs.cfg Hannes Laimer
2022-03-14 9:26 ` [pve-devel] [PATCH qemu-server v3 3/3] " Hannes Laimer
2022-03-16 7:15 ` [pve-devel] [PATCH-SERIES v3] fix #3903: remove vmid from jobs.cfg on destroy Thomas Lamprecht
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=20220314092657.48696-1-h.laimer@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=pve-devel@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.