Not able to use pveceph purge to completely remove ceph

[psionic]

Thanks to all in this thread, restored my Ceph cluster to working condition with the info in this thread...

 

[damon1]

So here we go, my buddy and I worked through the issue, I do believe this is a ceph bug. We both work as high level ITs. In short, do all the stuff listed above, once done run these 3 commands and you should have a working package again. It appears after doing a purge or removing ceph ceph-mon ceph-osd one of the shared libraries phyiscally goes bye bye however the environment still thinks the library is present.

Run initial repair on all ceph packages:

for i in $(apt search ceph | grep installed | awk -F/ '{print $1}'); do apt reinstall $i; done

Reconfigure the deb packages:

dpkg-reconfigure ceph-base
dpkg-reconfigure ceph-mds
dpkg-reconfigure ceph-common
dpkg-reconfigure ceph-fuse

Rerun the same repair script:

for i in $(apt search ceph | grep installed | awk -F/ '{print $1}'); do apt reinstall $i; done

Run the installer:

pveceph install

Should do the job!

102020
You are Da Man - worked a treat.

 

[paulholyoak]

So here we go, my buddy and I worked through the issue, I do believe this is a ceph bug. We both work as high level ITs. In short, do all the stuff listed above, once done run these 3 commands and you should have a working package again. It appears after doing a purge or removing ceph ceph-mon ceph-osd one of the shared libraries phyiscally goes bye bye however the environment still thinks the library is present.

Run initial repair on all ceph packages:

for i in $(apt search ceph | grep installed | awk -F/ '{print $1}'); do apt reinstall $i; done

Reconfigure the deb packages:

dpkg-reconfigure ceph-base
dpkg-reconfigure ceph-mds
dpkg-reconfigure ceph-common
dpkg-reconfigure ceph-fuse

Rerun the same repair script:

for i in $(apt search ceph | grep installed | awk -F/ '{print $1}'); do apt reinstall $i; done

Run the installer:

pveceph install

Should do the job!

thank you!! I've been battling with this for days on a new proxmox cluster and this solved it.