Hi,
When you mentioned that you changed your project name did you receive any other error messages in that process, because the shared error message you provided is more related to the fact that your zones 'us-west1-b' and 'us-east1-b' have no resources available.
Our goal is to make sure that there are available resources in all zones. This type of issue is rare. When a situation like this occurs, or is about to occur, our team is notified immediately and the issue is investigated and mitigated.
I tried to create instances in the mentioned problematic zones to make sure if the issue is still persisting, but I was able to create and start them.
On the other hand, I want to share a detailed procedure for
moving instances between zones to help you start your instance in another zone with available resources to see if you have the same issue again. The easiest way would be to use the 'gcloud compute instances move' command described there. Please, however, check out the requirements and precautions related to moving instances to avoid issues during moving your instances.