Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Equinix Metal - removal of "facilities" API support in favor of "metro" API #13243

Open
vielmetti opened this issue Apr 4, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@vielmetti
Copy link

What happened?

With this change, any system that's provisioned specifying a facility will get a 422 error
from the API. (From reading the code at

https://github.com/kubermatic/kubermatic/blob/main/pkg/machine/provider/equinixmetal.go

it appears that the facility support is still here; I don't know if it's always used.)

How to reproduce the issue?

Specific an Equinix Metal facility in the configuration; it should fail

if len(config.Facilities) == 0 {

(I don't have a better reproducer than that, but that's the line you want to hit)

How is your environment configured?

  • KKP version: any
  • Shared or separate master/seed clusters?: any

Provide your KKP manifest here (if applicable)

# paste manifest here

What cloud provider are you running on?

Equinix Metal

What operating system are you running in your user cluster?

any

Additional information

Happy to provide a test environment to validate if needed, this is from inspection of the code. I don't
know how things will error out.

@vielmetti vielmetti added the kind/bug Categorizes issue or PR as related to a bug. label Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant