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

AKOO should check if ControlPlaneEndpoint is FQDN before setting to HA service #178

Closed
1 of 6 tasks
lubronzhan opened this issue Feb 23, 2024 · 1 comment
Closed
1 of 6 tasks

Comments

@lubronzhan
Copy link
Contributor

Bug description
In AKOO 1.9 It's not checking whether the cluster.Spec.ControlPlaneEndpoint.Host is FQDN or not, before updating the service's loadbalancerIP here, that's why this is failing. It only checks here 

So it sets FQDN as service.spec.loadbalancerIP, then AKO will have issue with it and can't update the backend server pool

2024-01-09T13:16:20.669Z WARN rest/dequeue_nodes.go:806 key: admin/tkg-system-mgmt--tkg-system-tkg-system-mgmt-control-plane, msg: problem in processing request for: VsVip
2024-01-09T13:16:20.669Z INFO rest/dequeue_nodes.go:807 key: admin/tkg-system-mgmt--tkg-system-tkg-system-mgmt-control-plane, msg: error str: Encountered an error on PUT request to URL https://10.97.48.5//api/vsvip/vsvip-3628bde3-2707-4974-9a1c-f908aec5b209: HTTP code: 400; error from Avi: map[error:tkg-system-mgmt--tkg-system-tkg-system-mgmt-control-plane has invalid virtual ipv4 address mgmt.tanzu.bitc.int.tele2.com]

Affected product area (please put an X in all that apply)

  • Docs
  • Installation
  • Plugin
  • Security
  • Test and Release
  • User Experience

Expected behavior

Steps to reproduce the bug

Version (include the SHA if the version is not obvious)

Environment where the bug was observed (cloud, OS, etc)

Relevant Debug Output (Logs, manifests, etc)

@lubronzhan
Copy link
Contributor Author

Completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant