public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Oguz Bektas <o.bektas@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v3 container 2/2] clear machine-id also after container clone
Date: Thu, 27 May 2021 11:26:01 +0200	[thread overview]
Message-ID: <20210527092601.148400-3-o.bektas@proxmox.com> (raw)
In-Reply-To: <20210527092601.148400-1-o.bektas@proxmox.com>

pass $clone=1 to avoid removing the file. instead we truncate it to an
empty file

Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
---
v2->v3:
* clear machine-id at the end of clone task worker

 src/PVE/API2/LXC.pm | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
index a9ea3a6..d5c12dc 100644
--- a/src/PVE/API2/LXC.pm
+++ b/src/PVE/API2/LXC.pm
@@ -1590,6 +1590,12 @@ __PACKAGE__->register_method({
 		die "clone failed: $err";
 	    }
 
+	    my $lastconf = PVE::LXC::Config->load_config($newid);
+	    my $rootdir = PVE::LXC::mount_all($newid, $storecfg, $lastconf, 1);
+	    my $lxc_setup = PVE::LXC::Setup->new($lastconf, $rootdir);
+	    $lxc_setup->clear_machine_id($lastconf, 1);
+	    PVE::LXC::umount_all($newid, $storecfg, $lastconf, 1);
+
 	    return;
 	};
 
-- 
2.20.1





  parent reply	other threads:[~2021-05-27  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27  9:25 [pve-devel] [PATCH v3 container 0/2] fix #3443: unique machine-id for containers Oguz Bektas
2021-05-27  9:26 ` [pve-devel] [PATCH v3 container 1/2] setup: clear /etc/machine-id for newly created containers Oguz Bektas
2021-06-10 11:47   ` Fabian Grünbichler
2021-06-10 12:04     ` Oguz Bektas
2021-05-27  9:26 ` Oguz Bektas [this message]
2021-06-10 11:51   ` [pve-devel] [PATCH v3 container 2/2] clear machine-id also after container clone Fabian Grünbichler

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=20210527092601.148400-3-o.bektas@proxmox.com \
    --to=o.bektas@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal