From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Friedrich Weber <f.weber@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager stable-7] pve7to8: content-dirs check: skip paths that cannot be resolved
Date: Thu, 15 Jun 2023 16:47:44 +0200 [thread overview]
Message-ID: <66343ef8-e117-a795-6d04-dca1c77de157@proxmox.com> (raw)
In-Reply-To: <20230615132231.702195-1-f.weber@proxmox.com>
Am 15/06/2023 um 15:22 schrieb Friedrich Weber:
> The current inequality check for content-dirs does not correctly
> handle the case in which `abs_path` returns undef. This can result in
> confusing warnings:
>
> storage [...] uses directory for multiple content types [...]
>
> Fix this by skipping paths for which `abs_path` returns undef. This
> matches the behavior of the actual content-dirs check in PVE 8 [0].
>
> [0]: https://git.proxmox.com/?p=pve-storage.git;a=commit;h=09f1f847a
>
> Fixes: ea0a4f1943ffafe94282afc800d5720db45df198
> Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
> ---
> PVE/CLI/pve7to8.pm | 1 +
> 1 file changed, 1 insertion(+)
>
>
applied, thanks!
prev parent reply other threads:[~2023-06-15 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 13:22 [pve-devel] " Friedrich Weber
2023-06-15 14:47 ` Thomas Lamprecht [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=66343ef8-e117-a795-6d04-dca1c77de157@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.weber@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