weizhouapache commented on issue #13989:
URL: https://github.com/apache/cloudstack/issues/13989#issuecomment-5582120452

   > I ran into this same issue rebuilding my lab. For now we're just holding 
our KVM hosts on Ceph 20.2.2. Anyone building a fresh CS install with Ceph 
Tentacle (latest) is going to hit this issue.
   > 
   > RE: PR [#13991](https://github.com/apache/cloudstack/pull/13991) - while 
it is required, I don't think the PR fixes this on its own. The PR fixes the 
qemu-img operations (template copy to primary, volume copies, snapshot backup) 
so it is necessary, but there's also the error in the log above coming from 
libvirt. That libvirt log is where libvirt's RBD storage backend sets 
`auth_supported` itself when it opens the connection for the pool, so the 
connection to the storage pool will still fail on a 20.2.4 client with the PR 
applied. As far as I can see libvirt hasn't fixed this yet and Ceph hasn't 
reverted the removal.
   > 
   > Proxmox ran into the same thing 
(https://bugzilla.proxmox.com/show_bug.cgi?id=7961) and ended up putting the 
option back in their own Ceph build rather than waiting on upstream.
   > 
   > So [#13991](https://github.com/apache/cloudstack/pull/13991) is still 
needed for the qemu-img side, but this issue probably needs to stay open until 
libvirt catches up. Not sure if there's anything else that should be done 
communications wise - as there will be deployments failing if people are just 
using cepf-tentacle (latest).
   
   @MitchDrage agreed on all counts — I hit the exact same thing while triaging 
this for a user, and it lines up with your read.
   
   Confirmed by reproducing directly with `virsh pool-create` (bypassing 
CloudStack entirely) against a Ceph Tentacle 20.2.4 cluster: even with #13991 
applied, `LibvirtStorageAdaptor.createRBDStoragePool()` fails identically, 
because the failing `auth_supported` call lives entirely inside libvirt's own C 
code (src/storage/storage_backend_rbd.c, `virStorageBackendRBDOpenRADOSConn`) — 
it's hardcoded there and treated as fatal, with no CloudStack-side string or 
config reaching it. 
   
   [#13991](https://github.com/apache/cloudstack/issues/13991) is still 
correct/needed for the qemu-img-driven paths (template seeding, volume/snapshot 
copies), but the storage-pool-creation path is a separate libvirt bug, not 
something CloudStack code can route around.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to