You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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 hereSo it sets FQDN as service.spec.loadbalancerIP, then AKO will have issue with it and can't update the backend server pool
Affected product area (please put an X in all that apply)
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)
The text was updated successfully, but these errors were encountered: