From: Severen Redwood via pve-devel <pve-devel@lists.proxmox.com>
To: a.lauterer@proxmox.com
Cc: Severen Redwood <severen.redwood@sitehost.co.nz>,
pve-devel@lists.proxmox.com, t.lamprecht@proxmox.com
Subject: Re: [pve-devel] [PATCH container v2] api: record CT ID as used after a container is destroyed
Date: Tue, 5 Nov 2024 13:53:41 +1300 [thread overview]
Message-ID: <mailman.711.1730768045.332.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <0c3fcb3d-6367-403b-968a-d73042853c33@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 4410 bytes --]
From: Severen Redwood <severen.redwood@sitehost.co.nz>
To: a.lauterer@proxmox.com
Cc: pve-devel@lists.proxmox.com, t.lamprecht@proxmox.com
Subject: Re: [pve-devel] [PATCH container v2] api: record CT ID as used after a container is destroyed
Date: Tue, 5 Nov 2024 13:53:41 +1300
Message-ID: <ba5t63z7iwekm7iejhguzrjxlnpp2d27a4j7flrdcmxturpkfq@lsioezbx572v>
Hi Aaron,
On Thu, Oct 31, 2024 at 06:27:43PM +0100, Aaron Lauterer wrote:
> This is missing a
>
> use PVE::UsedVmidList;
>
> at the top of the file. Otherwise running
>
> pct destroy {vmid}
>
> will result in the following error:
>
> Undefined subroutine &PVE::UsedVmidList::add_vmid called at
> /usr/share/perl5/PVE/API2/LXC.pm line 799.
>
> This doesn't seem to be necessary in the qemu-server repo, but I did not
> investigate further how pulling in dependencies works there.
Thanks for catching this! It's strange that it's not necessary in
`PVE::API2::Qemu`... Either way, I think it makes sense to explicitly use the
module in both files, so I'll update the patches to do that.
Thanks,
Severen
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-05 0:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241004050957.441759-1-severen.redwood@sitehost.co.nz>
2024-10-04 5:07 ` [pve-devel] [PATCH manager v2 1/2] close #4369: api: optionally only suggest unique IDs Severen Redwood via pve-devel
2024-10-04 5:07 ` [pve-devel] [PATCH manager v2 2/2] close #4369: ui: add datacenter option for unique VM/CT IDs Severen Redwood via pve-devel
2024-10-04 5:07 ` [pve-devel] [PATCH container v2] api: record CT ID as used after a container is destroyed Severen Redwood via pve-devel
2024-10-04 5:07 ` [pve-devel] [PATCH qemu-server v2] api: record VM ID as used after a virtual machine " Severen Redwood via pve-devel
2024-10-04 5:07 ` [pve-devel] [PATCH cluster v2 5/6] cluster files: add used_vmids.list Severen Redwood via pve-devel
2024-10-04 5:07 ` [pve-devel] [PATCH cluster v2 6/6] datacenter config: add unique-next-id to schema Severen Redwood via pve-devel
2024-10-30 2:29 ` [pve-devel] [PATCH SERIES v2] Add ability to prevent suggesting previously used VM/CT IDs Severen Redwood via pve-devel
[not found] ` <20241004050957.441759-2-severen.redwood@sitehost.co.nz>
2024-10-31 13:10 ` [pve-devel] [PATCH manager v2 1/2] close #4369: api: optionally only suggest unique IDs Aaron Lauterer
[not found] ` <20241004050957.441759-4-severen.redwood@sitehost.co.nz>
2024-10-31 17:27 ` [pve-devel] [PATCH container v2] api: record CT ID as used after a container is destroyed Aaron Lauterer
2024-11-05 0:53 ` Severen Redwood via pve-devel [this message]
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=mailman.711.1730768045.332.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=severen.redwood@sitehost.co.nz \
--cc=t.lamprecht@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox