Comment 1 for bug 1846820

It's blowing up trying to get the service catalog from keystone to get the endpoint URL for the placement service. We could do something like in bug 1807219 and offload that placement SchedulerReportClient instantiation to a singleton lazy-load pattern so it's not hit when conductor starts up but if keystone is having problems we could just fail later when trying to lazy-load the client, so I'm not sure if that's helpful. I'd consider this very low priority since the root problem appears to be in keystone.