I have not been able to deploy new canisters to my subnet of choice, which I already have ~15 canisters on.
I can make canisters without a specified subnet. I was always was able to make new ones with this command up until about 1-2 months ago (when I realized this failure):
As a workaround: If a canister calls aaaaa-aa:create_canister the newly created canister will be on the same subnet. If you use one of your canisters on that subnet to create a new one you’ll have a new one there
Hey @evanmcfarland! Just to put as all on the correct page, this is the latest proposal that updates the list of authorized subnets. If you take a look at the payload you will see that your preferred subnet got closed because it has more than 400GB in total state. Sorry for the inconvenience and hope that the explanation helps!
If you are interested on how do we generate the list of subnets we intend to close / open you can find it on dre repo.