public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Anthony Galica <anthony.galica@hitachivantara.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: RE: :Cluster::cfs_lock_domain - bizarre issue
Date: Fri, 24 Jul 2026 09:38:19 +0000	[thread overview]
Message-ID: <IA1PR08MB8621406F1260D45BBE25ACE8F8CF2@IA1PR08MB8621.namprd08.prod.outlook.com> (raw)
In-Reply-To: <CH3PR08MB8612F0B93027406647945A73F8CF2@CH3PR08MB8612.namprd08.prod.outlook.com>

I also see this same issue with PVE::Tools::file_set_contents().


-----Original Message-----
From: Anthony Galica <anthony.galica@hitachivantara.com> 
Sent: Friday, July 24, 2026 1:28 AM
To: pve-devel@lists.proxmox.com
Subject: PVE::Cluster::cfs_lock_domain - bizarre issue

Hi everyone,

I am getting a very strange issue from PVE::Cluster::cfs_lock_domain, but only when it is called via activate_volume.  

For each test, I restarted these services first:
systemctl restart pveproxy pvedaemon pvestatd pvescheduler spiceproxy pve-cluster

I have asked Gemini for help, and it continues to suggest various things, but none of them work.

Consider this code:

sub _lock_name {
	my ($context) = @_;

	use constant CONNECTION_LOCK_NAME_HEADER => 'connection-lock-';
	my $serial = $context->serial(); # returns 810050
	return CONNECTION_LOCK_NAME_HEADER . "$serial"; }

my $lock_name = _lock_name($context);
PVE::Cluster::cfs_lock_domain($lock_name, _CONNECTIONS_LOCK_TIMEOUT,  sub { print(""); });

This will *always* fail from within activate_volume (or another subroutine in the same stack) with this error:

	TASK ERROR: cfs-lock 'domain-connection-lock-810050' error: Insecure dependency in mkdir while running with -T switch at /usr/share/perl5/PVE/Cluster.pm line 639.

It also fails if I use sprintf instead.  Or if I append an extra "" (Gemini suggestion), etc.  

When this happens, /etc/pve/priv/lock is empty, and no other calls have been made to activate_volume.

The above code works fine if invoked from a subroutine that was called via the command line.

Now for the really strange part: if I change _lock_name to return the exact same string, only without any formatting, it will work.

Working code:

sub _lock_name {
	my ($context) = @_;

	return 'connection-lock-810050';
}

Does anyone have any insight as to why this is happening and how I can get around it?

Thank you!
Anthony





  reply	other threads:[~2026-07-24  9:53 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 11:56 [PATCH many 00/29] notifications: add nested match expressions Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 01/29] add new proxmox-match-expression crate Lukas Wagner
2026-07-24  6:46   ` Arthur Bied-Charreton
2026-07-09 11:56 ` [PATCH proxmox 02/29] notify: promote matcher to dir-style module Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 03/29] notify: fix doc comment Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 04/29] notify: matcher: break out severity matcher into submodule Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 05/29] notify: matcher: break out field " Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 06/29] notify: matcher: break out calendar " Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 07/29] notify: matcher: calendar: add basic unit test Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 08/29] notify: matcher: add InlineSeverityMatcher Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 09/29] notify: matcher: add InlineFieldMatcher Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 10/29] notify: matcher: add InlineCalendarMatcher Lukas Wagner
2026-07-24  6:47   ` Arthur Bied-Charreton
2026-07-24  9:43     ` Wolfgang Bumiller
2026-07-09 11:56 ` [PATCH proxmox 11/29] notify: matcher: add expression support Lukas Wagner
2026-07-24  6:59   ` Arthur Bied-Charreton
2026-07-24  8:27     ` PVE::Cluster::cfs_lock_domain - bizarre issue Anthony Galica
2026-07-24  9:38       ` Anthony Galica [this message]
2026-07-25  7:14         ` :Cluster::cfs_lock_domain " Anthony Galica
2026-07-09 11:56 ` [PATCH proxmox 12/29] notify: api: support new expression parameter Lukas Wagner
2026-07-24  6:46   ` Arthur Bied-Charreton
2026-07-24 10:01     ` Wolfgang Bumiller
2026-07-24 11:38       ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox 13/29] notify: api: add `get_matcher_as_expression` Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox 14/29] notify: migrate PBS's and PVE's default matcher to expression syntax Lukas Wagner
2026-07-24  6:47   ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox 15/29] notify: move legacy matcher keys behind feature flag Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 16/29] notification: increase matcher window width Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 17/29] notifications: matcher: add support for match expressions Lukas Wagner
2026-07-24  6:45   ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 18/29] notification: matcher: add better calendar editor Lukas Wagner
2026-07-24  6:46   ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 19/29] notifications: matcher: consistently use title case for UI elements Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 20/29] notification: opt into 'legacy-matchers' feature in proxmox-notify Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 21/29] api: notification: add 'migrate-to-expression' parameter to get_matcher Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 22/29] ui: notification: enable new matcher UI Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 23/29] notify: matcher: pass matcher config / updater directly Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 24/29] notify: opt into 'legacy-matchers' feature in proxmox-notify Lukas Wagner
2026-07-24  6:48   ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 25/29] notify: add 'migrate_to_expression' parameter for get_matcher Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 26/29] api: notification: pass config/updater directly to rust bindings Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 27/29] api: notification: get_matcher: add 'migrate-to-expression' parameter Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 28/29] api: notification: add 'expression' to matcher parameter schema Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 29/29] ui: notification: enable new matcher UI Lukas Wagner
2026-07-24  6:44 ` [PATCH many 00/29] notifications: add nested match expressions Arthur Bied-Charreton
2026-07-24  6:53   ` Arthur Bied-Charreton

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=IA1PR08MB8621406F1260D45BBE25ACE8F8CF2@IA1PR08MB8621.namprd08.prod.outlook.com \
    --to=anthony.galica@hitachivantara.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