Equinix provider does not filter FAN subnets when querying equinix API
Bug #1941911 reported by
Achilleas Anagnostopoulos
This bug report is a duplicate of:
Bug #1941912: Equinix provider does not filter FAN subnets when querying equinix API.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Medium
|
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.
| Changed in juju: | |
| milestone: | 2.9.13 → 2.9.14 |
| Changed in juju: | |
| milestone: | 2.9.14 → 2.9.15 |
Revision history for this message
| Achilleas Anagnostopoulos (achilleasa) wrote | #1 |
| Changed in juju: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Duplicate of https:/