From: Erik Fastermann <e.fastermann@proxmox.com>
To: Elias Huhsovitz <e.huhsovitz@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH container v2] fix #7164: lxc: restore: apply password and ssh keys during container restore
Date: Fri, 31 Jul 2026 10:24:54 +0200 [thread overview]
Message-ID: <a49f6013-0178-495f-948e-69251f491132@proxmox.com> (raw)
In-Reply-To: <DKBUEEBT204W.2R14F2FDBX4U@proxmox.com>
[snip]
>>> Add `check_systemd_nesting` to the `post_restore_hook`.
>>
>> Why is this added? A rational here would be helpful. If the reason is
>> just symmetry with `post_create_hook`, we might need to be careful here,
>> as this could introduce new unwanted failure conditions. I have not
>> checked in detail, but some of the code can die.
>
> I believed adding this check might make the restore process more resiliant
> since the user might get important warnings early, thus reducing the amount
> of troubleshooting needed.
>
> But as you pointed out, this could lead to a regression.
>
> Since a restore is technically a creating a new contaienrs, i felt as
> though adding this check made sense. Perhaps the `die` is a good thing?
> Alerting the user early regarding potential issues, might be beneficial.
>
> I am curious to know what your opinion is on this! After more consideration
> I am strongly considering omitting the check.
>
More checks are usually good and I currently don't see a concrete
use-case where having this check would break something. I still would
prefer if this was an additional patch as it is unrelated to the
original fix.
[snip]
next prev parent reply other threads:[~2026-07-31 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 8:25 [PATCH container v2] fix #7164: lxc: restore: apply password and ssh keys during container restore Elias Huhsovitz
2026-07-29 14:20 ` Erik Fastermann
2026-07-30 10:43 ` Elias Huhsovitz
2026-07-31 8:24 ` Erik Fastermann [this message]
2026-07-31 12:08 ` superseded: " Elias Huhsovitz
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=a49f6013-0178-495f-948e-69251f491132@proxmox.com \
--to=e.fastermann@proxmox.com \
--cc=e.huhsovitz@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