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

GetManagementPort returning an error causing floating ip mapping failure. #1921

Closed
mouad-eh opened this issue Mar 4, 2024 · 2 comments
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@mouad-eh
Copy link

mouad-eh commented Mar 4, 2024

/kind bug

What steps did you take and what happened:
I am trying to create a single node openstack cluster (without-lb flavor) using clusterctl command. The infrastructure is provisioned and I can see that in the openstack dashboard but the mapping between the floating ip and the fixed ip is not happening.

What did you expect to happen:
CAPO automatically maps between the Foating IP and the fixed IP.

Anything else you would like to add:

  • the openstack cloud is created by using microstack

  • when I did the troubleshooting, I find out that this line of code is failing

  • Here are the logs from the CAPO-controller-manager:

image
  • Here is the status of the Cluster Resource:
image

Environment:

  • Cluster API Provider OpenStack version (Or git rev-parse HEAD if manually built): v0.9.0
  • Cluster-API version: v1.6.1
  • OpenStack version: 5.2.0
  • Minikube/KIND version: I am using a kubeadm cluster (kubernetes version v1.29.1)
  • Kubernetes version (use kubectl version): v1.28.3(client) - v1.29.1(server)
  • OS (e.g. from /etc/os-release): Ubuntu 22.04.3 LTS
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 4, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 2, 2024
@mdbooth
Copy link
Contributor

mdbooth commented Jun 3, 2024

This looks like a configuration quirk relating to this deployment. CAPO is trying to access the OpenStack endpoint on localhost and doesn't find it there.

@mdbooth mdbooth closed this as completed Jun 3, 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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
Status: Done
Development

No branches or pull requests

4 participants