Comment 1 for bug 1409012

This is caused by the fact a newly started scheduler needs to receive stat update broadcasts to know what backends are out there.

Possibly fixable by modifying the scheduler not to listen for incoming create (etc) requests until the stats broadcast period (30 seconds by default) has passed.

Note that this same problem occurs if you spin up a second (or more) scheduler, e.g. for load balancing or active/active H/A - the new scheduler will fail all requests it receives until it hears from backends.