Good afternoon, I've continued my testing and research on this test case, and I've tried out a few more options with their results: 1. I attempted to attach a new disk to the storage hosts through the "qemu-img create" and "virsh attach-disk" commands. The HEALTH_WARN flag when checking ceph health doesn't allow the storage hosts to be locked to add the new disks, so they must be forced locked. Once locked, the disks appear with a size_gib attribute of 0 despite having the same size as the other disk images. Before adding the disk image: [cid:image002.png@01D500E8.AB640850] The created image on the left, a default image on the right: [cid:image003.png@01D500E8.AB640850] [cid:image004.png@01D500E8.AB640850] After adding the disk image: [cid:image005.png@01D500E8.AB640850] 2. Along with this, in my repo where I ran setup and provisioning, the .xml files for the VMs stored in "Qemu", the only two disks available are sda and sdb. Attempting to modify this file before setup to include a third disk for test purposes does not help in adding a new disk to the system. [cid:image006.png@01D500E8.AB640850] 3. An attempt was made to create a replication value of min 1 and size 3. This configuration did not work and the ceph cluster's PGs remain stuck and unable to peer or host. [cid:image007.png@01D500E8.AB640850] [cid:image008.png@01D500E8.AB640850] I attach this report as a reply to this thread for easier access to the rest of the process. Thank you, [cid:image001.png@01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer.