Comment 13 for bug 1444841

I'm trying to pursue options to prevent a user from getting into this situation in the first place. It seems if we can detect that the user is requesting an instance in the CONF.default_availability_zone explicitly but that's not actually in an aggregate, we could return a 400 (maybe that would have to take into account CONF.default_schedule_zone if it's set).