Rbd: couldn't connect to cluster

Firm

Renowned Member
Oct 27, 2015
40
1
73
Hi,

I has PVE 4.2 with Ceph installed with help of pveceph. The problem is that when I try to create CT/VM on RBD volume it ends with error:
Code:
TASK ERROR: rbd error: rbd: couldn't connect to the cluster!

I was able to trace calls to rbd binary which is executed with "--auth_supported none" in command line. I wonder why PVE GUI is using "none" while I has "cephx" authentication type in /etc/ceph/ceph.conf.

P.S. Changing none to cephx leads to successful executions of rbd command.

Regards,
Alex
 
I was able to trace calls to rbd binary which is executed with "--auth_supported none" in command line. I wonder why PVE GUI is using "none" while I has "cephx" authentication type in /etc/ceph/ceph.conf.

Because you forgot to upload the key to /etc/pve/priv/ceph/${storeid}.keyring ?
 
  • Like
Reactions: fibo_fr
dietmar, you're right. I missed this step in manual. Now the Status looks like:
Code:
stopped: rbd error: got lock timeout - aborting command

Wonder if it's related to
Code:
pgmap v67: 64 pgs: 64 stale+active+undersized+degraded; 0 bytes data, 197 MB used, 22315 GB / 22315 GB avail
 
Last edited:
  • Like
Reactions: fibo_fr
It was definitely problem with ceph installation. Using separate network segments via public/cluster network parameters leads to problem with osd daemon can't report to mon daemon (still checking why). Using single network segment is ok.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!