From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH manager 1/2] fix #6779: pveupdate: renew already expired certificates
Date: Thu, 23 Oct 2025 10:20:52 +0200 [thread overview]
Message-ID: <176120764513.279713.1182718900439262820.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250909100529.415836-1-f.gruenbichler@proxmox.com>
On Tue, 09 Sep 2025 12:04:47 +0200, Fabian Grünbichler wrote:
> if nodes are offline for a longer period of time, they might not be renewed by
> pveupdate before they expire. the `verify` call here just serves as an
> extra safeguard to prevent accidental overwriting of certificates not actually
> signed by the cluster CA, checking the expiry time servers no purpose.
>
>
Applied with Fiona's R-b, thanks!
[1/2] fix #6779: pveupdate: renew already expired certificates
commit: 6ec35c4ff917512d9091d97b602a0188d435aeeb
[2/2] pveupdate: improve cert renew log messages
commit: 351df678af73ea63748637ce3859ff87d85090e9
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
_______________________________________________
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-10-23 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 10:04 [pve-devel] " Fabian Grünbichler
2025-09-09 10:04 ` [pve-devel] [PATCH manager 2/2] pveupdate: improve cert renew log messages Fabian Grünbichler
2025-10-22 13:09 ` Fiona Ebner
2025-10-22 13:09 ` [pve-devel] [PATCH manager 1/2] fix #6779: pveupdate: renew already expired certificates Fiona Ebner
2025-10-23 8:20 ` Fabian Grünbichler [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=176120764513.279713.1182718900439262820.b4-ty@proxmox.com \
--to=f.gruenbichler@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