I cannot finish earlier started deployment of my dapp

I cannot deploy a new canister of my app to the subnet that other my canisters are deployed in:

DFX_IDENTITY=Zon make NETWORK=ic deploy
dfx canister create --network ic CanDBPartition
⠄ Creating canister CanDBPartition...                                                                                                                                                   created-at-time for canister CanDBPartition is 1738256775989293187.
Error: Failed to create canister 'CanDBPartition'.
Caused by: Failed to create canister via cycles ledger.
Caused by: Cycles ledger failed to create canister: Subnet opn46-zyspe-hhmyp-4zu6u-7sbrh-dok77-m7dch-im62f-vyimr-a3n2c-4ae does not exist or um5iw-rqaaa-aaaaq-qaaba-cai is not authorized to deploy to that subnet.

Should I spread a part of my app into another subnet? (Which one? Please, point me how to choose a subnet.) Should I back it up and redeploy anew (a time-consuming thing to accomplish)?

Maybe the admins of this subnet can give me access?

My cycles ledger is um5iw-rqaaa-aaaaq-qaaba-cai. My user principal is: 2qop4-5u6dp-g4pmz-lpzyb-hjv6c-be66l-twfuo-ynxgi-hb456-g75bi-rae.

The dapp in question is https://zoncircle.com

Were you able to create the canister in the required subnet? I encountered the same error.

I found a way to make my app work without deploying additional canisters. But it is unacceptable in the future to remain in this subnet.

I need to backup my app and redeploy it in another subnet.

It would be better, if there were a way (feature suggestion!) to move canisters between subnets.

If one of your canisters calls aaaaa-aa:create_canister then the new canister will be created on the same subnet as the calling canister. If you want to create the new canister via dfx then you need to pick a new subnet and specify it with --subnet <id>

There’s design docs about this floating around internally already…

Canister migration is part of the upcoming Flux milestone.

1 Like