I just reinstalled the whole thing from scratch, after going to Ubuntu MaaS and "Release -> Deploy" and then, running `openstack-ansible setup-everything.yml` again.
I know that my fresh Ceph cluster doesn't come HEALTHY after `openstack-ansible ceph-install.yml` but, I decided to proceed anyway, just to test it again as it was.
It fails on the same spot!
I noticed that when Ceph is in bad shape, and I try to create a Cinder Volume on it, the "cinder-volume" agents turns itself "DOWN", while the cinder-volume process is still running inside of cinder-container!
So, this means that cinder-volume isn't in a "up" state, then, I believe that it's triggering this bug as well!
What I'm going to do next? Same thing I did before!
Which was to bring Ceph to a HEALTHY state and try `openstack-ansible os-cinder-install.yml` again!
I just reinstalled the whole thing from scratch, after going to Ubuntu MaaS and "Release -> Deploy" and then, running `openstack-ansible setup-everythin g.yml` again.
I know that my fresh Ceph cluster doesn't come HEALTHY after `openstack-ansible ceph-install.yml` but, I decided to proceed anyway, just to test it again as it was.
It fails on the same spot!
I noticed that when Ceph is in bad shape, and I try to create a Cinder Volume on it, the "cinder-volume" agents turns itself "DOWN", while the cinder-volume process is still running inside of cinder-container!
So, this means that cinder-volume isn't in a "up" state, then, I believe that it's triggering this bug as well!
What I'm going to do next? Same thing I did before!
Which was to bring Ceph to a HEALTHY state and try `openstack-ansible os-cinder- install. yml` again!