D dbrega Member Sep 6, 2025 35 0 6 Thursday at 01:15 #1 I have this warning in ceph: I have already applied the ceph migration guide. What should I do to fix these warnings? Thanks in advance.
I have this warning in ceph: I have already applied the ceph migration guide. What should I do to fix these warnings? Thanks in advance.
SteveITS Well-Known Member Proxmox Subscriber Feb 6, 2025 906 390 68 Thursday at 01:39 #2 Did you see https://pve.proxmox.com/pve-docs/ch...ating service keys can remain for a few hours
VictorSTS Distinguished Member Proxmox Subscriber Oct 7, 2019 1,165 683 158 Spain Thursday at 09:57 #3 You are missing two steps. Once you are 100% sure packages are upgraded on every node and no external Ceph consumers without aes256k key type exist: To fix "1 auth client entities with insecure key types", use: Code: /usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys \ --apply \ --confirm-clients-refreshed client.admin To fix the "Monitors" warnings, use: Code: /usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys \ --apply \ --restrict-ciphers Then, another last warning similar to "rotating auth service keys using insecure key types" will pop up: wait a few hours for MON to rotate the keys automatically.
You are missing two steps. Once you are 100% sure packages are upgraded on every node and no external Ceph consumers without aes256k key type exist: To fix "1 auth client entities with insecure key types", use: Code: /usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys \ --apply \ --confirm-clients-refreshed client.admin To fix the "Monitors" warnings, use: Code: /usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys \ --apply \ --restrict-ciphers Then, another last warning similar to "rotating auth service keys using insecure key types" will pop up: wait a few hours for MON to rotate the keys automatically.