Equinix provider does not filter FAN subnets when querying equinix API

[Achilleas Anagnostopoulos]

When the provider prepares a new instance for which space constraints have been specified, it queries the equinix API for each subnet that Juju specifies in the StartInstance argument.

Before creating the instance (device in equinix terminology) the provider queries the equinix API to resolve each requested Juju subnet ID into a subnet CIDR which is then passed to the equinix create device API. However, the current provider implementation does not filter FAN subnets (FAN is automatically enabled on equinix metal) so the resolution for the FAN subnets fails (a 404 is returned back from the API) and the instance fails to be provisioned.

[Achilleas Anagnostopoulos (achilleasa)]

PR https://github.com/juju/juju/pull/13289 includes a fix for 2.9

[Juan M. Tirado (tiradojm)]

This is already merged into 2.9.