Comment 5 for bug 1429794

Revision history for this message
Bogdan Dobrelya (bogdando) wrote : Re: [BVT][OSTF][system_tests] Ubuntu with RadosGW env failed to boot instance from volume due to RadosGW free space issue

The free space looks to be reported as '0' until some moment of time, for example:
remote/node-1.test.domain.local/cinder-scheduler.log:2015-03-08T11:43:20.644020+00:00 debug: Received volume service update from rbd:volumes: {u'volume_backend_name': u'DEFAULT', u'free_capacity_gb': 0, u'driver_version': u'1.1.0', u'total_capacity_gb': 0, u'reserved_percentage': 0, u'vendor_name': u'Open Source', u'storage_protocol': u'ceph'}
remote/node-1.test.domain.local/cinder-scheduler.log:2015-03-08T11:44:03.764781+00:00 debug: Received volume service update from rbd:volumes: {u'volume_backend_name': u'DEFAULT', u'free_capacity_gb': 283, u'driver_version': u'1.1.0', u'total_capacity_gb': 296, u'reserved_percentage': 0, u'vendor_name': u'Open Source', u'storage_protocol': u'ceph'}

Here it was reported as '0' all the time before "2015-03-08T11:44:03.764781" and reported as '296' Gb later. Could thi race be related to the ceph readiness bug https://launchpad.net/bugs/1415954 ?