Search results

I've applied the patch and restarted pveproxy, but I get: Error Parameter verification failed. (400) net0: invalid format - format error net0.mtu: property is not defined in schema and the schema does not allow additional properties What else needs a restart to make it work? [edit: answering my...

Thanks @Alwin I was hoping to see a clear indication to keep the keyring option under [osd] since it's using a different path than the client keyring. The ending of the phrase: "[...], and remove it everywhere else." will still cause confusion and should be removed/reworded imho.

So we should KEEP in /etc/pve/ceph.conf: [osd] keyring = /var/lib/ceph/osd/ceph-$id/keyring Even though the instructions say: move the 'keyring' option into the 'client' section, and remove it everywhere else. Could the instruction be updated please...

Is this a generalized issue or only certain combination of hw/sw see this? And what about a fresh install of V6, does it have issues with corosync v3?

So once this patch makes it through, I can use a full cloud-config like https://cloudinit.readthedocs.io/en/latest/topics/examples.html ?

I need this feature as well.

Maybe it didn't come up during apt install due to it being 12.2.8 for radosgw and 12.2.10 for the rest of ceph? I already did the containerized setup and it works as an alternative... may actually be better this way so i can control the impact on the host.

I'm thinking that having the radosgw in a container might be a better idea... And goign from there, why isn't everything promox provides inside containers? hmm....

How did you get this to work? I'm facing dependency issues due to custom *-pve packages from Proxmox: [user@proxmox ~]# sudo apt-get install radosgw Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean...