Search results

ok, I'll wait for the next version. We are using EfficientIP as IPam, so as soon as it will be available, I'll surely take some time to make this IPam available for proxmox.

Hello, We've updated our test cluster to 6.3 and it seems that ipam would available for test. I've not been able to see any piece of code regarding to ipam, am I missing something ? We also have another strange bug, after clicking a zone in the tree view, nothing happen, and moving to another...

that's weird, lsblk sould report the uuid for the partition even if there's no FS on it ! I can assure you that partition get UUID ;) here is the output from my cluster : root@pve03:~# lsblk /dev/sdp -o NAME,FSTYPE,MOUNTPOINT,PARTTYPE,PARTLABEL,PARTUUID NAME FSTYPE MOUNTPOINT...

can you check the permittion of the /dev/sdc2 it should be ceph/ceph. "Ceph-disk " is taking care of that -> https://github.com/ceph/ceph/blob/jewel/src/ceph-disk/ceph_disk/main.py#L1224

Check the directory /var/lib/ceph it-self , it seems that it can't create the tmp dir !

This is strange, you should have a partuuid even if you don't have a FS on a partition. what's he output of sgdisk --info=2 /dev/sdc ? Ok let's try to generate the OSD from scratch the manuel way : // check that the table is GPT and generate 2 partitions, 1= total of disque - 5 Go , 2=5Go...

you don't need to peed any filesytem on /dev/sdc2 ( ceph will do it for you) but the partition type must be "45b0969e-9b03-4f30-b4c6-b4b80ceff106" -> https://github.com/ceph/ceph/blob/jewel/src/ceph-disk/ceph_disk/main.py#L52 sgdisk --change-name="2:ceph journal" \...

Can you symlink the journal to right partition (/dev/sdc2 in your case I think) ? what the result of : lsblk /dev/sdc -o NAME,FSTYPE,MOUNTPOINT,PARTTYPE,PARTLABEL,PARTUUID

ok it seems to fail to create the journal (line 167 of your log). Can you please : - mount /dev/sdc on a temporary dir dans check the journal file (sould be a symlink to a dev ) - try to see if the dev id is the same a in lsblk /dev/sdp -o NAME,FSTYPE,MOUNTPOINT,PARTTYPE,PARTLABEL,PARTUUID" It...

try without external journal ceph prepare --zap-disk /dev/sdc

Did you try to create OSD via native ceph command ? ex: ceph-disk prepare --journal-dev /dev/sdX1 /dev/sdY

look like a typo with the ceph-create-keys command, are your bootstrap key owned by ceph:ceph ?

hum, I've got the same issue, it seems that the bootstrap keys were losts. Check with : ceph auth list