From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, "Max R. Carrara" <m.carrara@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH v1 master ceph 0/2] Fix Ceph Squid Module Loading
Date: Wed, 16 Jul 2025 22:15:09 +0200 [thread overview]
Message-ID: <175269690760.3398976.7111454378932396506.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250716173956.980112-1-m.carrara@proxmox.com>
On Wed, 16 Jul 2025 19:39:54 +0200, Max R. Carrara wrote:
> Fix Ceph Squid Module Loading - v1
> ==================================
>
> The first patch provides a workaround for the PyO3 ImportError that's
> being thrown by the `restful` Ceph mgr Python module upon import.
> This fixes the following error:
>
> [...]
Patches seem relatively straight forward and I saw no new crash reports about
mgr modules in my test cluster, so:
Applied, thanks!
[1/2] provide workaround for PyO3 ImportError
commit: 51c4e16ffa4d46944b03b376e14aa92c7ca758ab
[2/2] mgr: fix errors regarding module imports and NOTIFY_TYPES attributes
commit: 099772ef89be90332860fc9606b70ee5ad6b6d38
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-16 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 17:39 [pve-devel] " Max R. Carrara
2025-07-16 17:39 ` [pve-devel] [PATCH v1 master ceph 1/2] provide workaround for PyO3 ImportError Max R. Carrara
2025-07-16 17:39 ` [pve-devel] [PATCH v1 master ceph 2/2] mgr: fix errors regarding module imports and NOTIFY_TYPES attributes Max R. Carrara
2025-07-16 20:15 ` 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=175269690760.3398976.7111454378932396506.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.carrara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.