From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
pve-user@pve.proxmox.com
Subject: Re: [PVE-User] Keyring problem for external rbds reported by pve8to9 check script
Date: Mon, 5 Jan 2026 12:48:53 +0100 [thread overview]
Message-ID: <442289bb-e9b4-4ce2-af41-3860b556a457@proxmox.com> (raw)
In-Reply-To: <mailman.1353.1763629724.362.pve-user@lists.proxmox.com>
Hi Rainer,
Am 20.11.25 um 10:08 AM schrieb Rainer Krienke via pve-user:
>
> Sorry, I need some more lines to describe the problem :-;
>
> I have a "PveCeph" cluster and there is a second PVE cluster "PVEnoceph" which is using external rbds located on "PveCeph" for vm storage. So all VMs (~80) are running on "PVEnoceph" cluster because it has more RAM and CPU Power but storage is located and provided by PveCeph.
>
> These two clusters are running fine with pve8.4, no problems. However running the pve9 check script /usr/bin/pve8to9 it shows an error:
>
> FAIL: The Ceph configuration of the following externally managed RBD
> storages needs to be updated:
> rbd_1 and rbd_2
>
> It also offers a script to fix this. But I am reluctant, since I would like to know first what is wrong now and how it can be fixed without breaking the running clusters?
you can run the script without breaking the running cluster. For why the
change is needed, see:
https://git.proxmox.com/?p=pve-manager.git;a=commit;h=3ac84223227e6ff78f3235376ca72c7f356a02f3
Best Regards,
Fiona
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next parent reply other threads:[~2026-01-05 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1353.1763629724.362.pve-user@lists.proxmox.com>
2026-01-05 11:48 ` Fiona Ebner [this message]
2025-11-20 11:29 Rainer Krienke via pve-user
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=442289bb-e9b4-4ce2-af41-3860b556a457@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-user@lists.proxmox.com \
--cc=pve-user@pve.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.