So after discussion with bug reporter, this is related to cluster cold boot-up process and requires radosgw to be monitored and restarted properly. It could be useful to use respawn upstart configuration or systemd control in the future. Nevertheless, the proper fix is to make radosgw retry connection until it finds running osds and can start providing the service. I am marking this bug as high and targeting assigning it to our ceph team for investigation
So after discussion with bug reporter, this is related to cluster cold boot-up process and requires radosgw to be monitored and restarted properly. It could be useful to use respawn upstart configuration or systemd control in the future. Nevertheless, the proper fix is to make radosgw retry connection until it finds running osds and can start providing the service. I am marking this bug as high and targeting assigning it to our ceph team for investigation