10 months ago
I was originally attempting to host my entire service on US West Metal, but have been forced onto non metal to have volumes. But when I try to add a volume to a service that is on non metal it does the following:
Pre deployment it says both are hosted on the same service
Once deployment starts the volume is switched to the same region but metal, this cannot be adjusted
The deployment then crashes with the debug: "Cannot migrate volumes between non-metal and metal regions. Please create a new volume instead."
Deleting the service and trying with a new one leads to the same problem
The region of the service the volume is attached to can be changed, but only to non metal volumes
I have tried various combinations of detachment, remake volume etc and cannot make them both have the same region, the only other avenue I thought could be the issue is that my preferred region in my settings is US West (Metal). This might be influencing the volume? But I can no longer switch this to a non metal server to check
4 Replies
Ok update:
I dismounted the volume and redeployed, this let me adjust the region of the instance to go back to US East Metal
I redeployed with these changes and then remounted the volume back to it
It seems to have built without any issues now, but given that the docs currently say that pro users can't have metal regions with volumes should I not proceed?
10 months ago
It's currently still in beta for Pro, with the only reason surrounding volume migrations, but you aren't doing a volume migration so you are fine to proceed.
To make it easier going forward, please feel free to enable the Metal Volumes feature flag in your account settings.
10 months ago
!s
Status changed to Solved brody • 10 months ago