search

kubernetes-sigs / cluster-api-provider-openstack

Cluster API implementation for OpenStack
https://cluster-api-openstack.sigs.k8s.io/
Apache License 2.0
297 stars 255 forks source link

Do not update floating ip if its already mapped correct #948

Closed tobiasgiese closed 3 years ago

tobiasgiese commented 3 years ago

/kind feature

Describe the solution you'd like

We had problems reconciling our clusters with legacy load balancers, which were migrated from Neutron LBaaS to Octavia. The issue is that the port has no project id associated. Therefore, a floating ip association will fail with the error:

Bad floatingip request: Cannot process floating IP association with Port a52bde06-ea25-4264-85b9-3af36628109b, since that port is owned by a different tenant.
hidekazuna commented 3 years ago

@tobiasgiese I wonder if this is not feature but bug. Update issue description using bug template, please.

tobiasgiese commented 3 years ago

/label kind/bug /unlabel kind/feature

k8s-ci-robot commented 3 years ago

@tobiasgiese: The label(s) /label kind/bug cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-openstack/issues/948#issuecomment-884861661): >/label kind/bug >/unlabel kind/feature Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.