Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

n2.xlarge.x86 gives error "Strange 2-bond ports conf - bond0: layer3, bond1: layer2-bonded" #306

Closed
displague opened this issue Jan 27, 2021 · 2 comments

Comments

@displague
Copy link
Member

displague commented Jan 27, 2021

When provisioning or updating a Packet provider v3.0.1 or older I receive the error message:

Strange 2-bond ports conf - bond0: layer3, bond1: layer2-bonded

This error is produced for most device_network_type type values.
Configuration with n2.xlarge.x86 devices (or any device with more than 2 network ports) are affected.

@displague
Copy link
Member Author

A recent API change is incompatible with this older version of the Packet provider.

Please update to v3.2.1 or use the Metal provider (equinix/terraform-provider-metal#1).

@displague
Copy link
Member Author

displague commented Jan 27, 2021

The specific API change that led to this:

  • Previously, even though no IPs were assigned to bond1, both bond0 and bond1 would (incorrectly) report as layer3.
  • Now, bond0 reports as layer3, while bond1 (correctly) reports as layer2-bonded.

The old network type detection (included in v3.0.1 and older of this provider) was not prepared for this change. Those versions error out on unexpected input.

equinixmetal-archive/packngo#185 introduced improvements to better handle 4 port devices. This was incorporated in v3.1.0 of this provider.

@displague displague unpinned this issue Jan 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant