Equinix provider does not filter FAN subnets when querying equinix API

Bug #1941912 reported by Achilleas Anagnostopoulos
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Achilleas Anagnostopoulos

Bug Description

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.

Revision history for this message
Achilleas Anagnostopoulos (achilleasa) wrote :

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

Revision history for this message
Juan M. Tirado (tiradojm) wrote :

This is already merged into 2.9.

Changed in juju:
status: In Progress → Fix Committed
Ian Booth (wallyworld)
Changed in juju:
milestone: 2.9.13 → 2.9.14
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers