From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, "Max R. Carrara" <m.carrara@proxmox.com>
Subject: [pve-devel] applied: [PATCH v1 squid-stable-8 ceph 0/2] Provide Workaround for PyO3 ImportError regarding Ceph Dashboard
Date: Tue, 15 Jul 2025 14:55:29 +0200 [thread overview]
Message-ID: <175258412701.1955303.2554417322712677704.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250715093237.650039-1-m.carrara@proxmox.com>
On Tue, 15 Jul 2025 11:32:35 +0200, Max R. Carrara wrote:
> Provide Workaround for PyO3 ImportError regarding Ceph Dashboard - v1
> =====================================================================
>
> In short, backport PR #62951 [0] and drop a patch that was made
> superfluous due to said backport.
>
> I tested this on my local bookworm/squid cluster—generating a
> self-signed cert worked without problems. The Dashboard is up and
> running.
>
> [...]
Applied to both master and squid-stable-8, thanks!
[1/2] backport workaround for PyO3 sub-interpreter ImportError
commit: e998bc5fcee5e247eaac961716047ee141304a90
[2/2] drop patch that disables generating self-signed certs for dashboard
commit: f9ff90eb591150177096b524b30c4f804059707b
_______________________________________________
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-15 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 9:32 [pve-devel] " Max R. Carrara
2025-07-15 9:32 ` [pve-devel] [PATCH v1 squid-stable-8 ceph 1/2] backport workaround for PyO3 sub-interpreter ImportError Max R. Carrara
2025-07-15 9:32 ` [pve-devel] [PATCH v1 squid-stable-8 ceph 2/2] drop patch that disables generating self-signed certs for dashboard Max R. Carrara
2025-07-15 12:55 ` 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=175258412701.1955303.2554417322712677704.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox