Example: I create a SMR for 2 c3.small.x86 devices in ewr1 over the API (with packngo). c3.small.x86 is not available in ewr1 (I think it's not a matter of capacity, it's just not offered there). The creation of the SMR succeeds, and the SMR API resource has empty "facilities" attribute.
First SMR was created with packngo, for c3.small.x86 in ewr1 (plan not available in facility), second was created with Console, it's for t1.small.x86 in ewr1 (plan available in faclity). You can see that the first resource has empty facilities field. The second is OK.
Example: I create a SMR for 2 c3.small.x86 devices in ewr1 over the API (with packngo). c3.small.x86 is not available in ewr1 (I think it's not a matter of capacity, it's just not offered there). The creation of the SMR succeeds, and the SMR API resource has empty "facilities" attribute.
First SMR was created with packngo, for c3.small.x86 in ewr1 (plan not available in facility), second was created with Console, it's for t1.small.x86 in ewr1 (plan available in faclity). You can see that the first resource has empty facilities field. The second is OK.
@displague This is an API issue, can you please post this to internal tracker?