apache / apache/cloudstack-kubernetes-provider
Load Balancer doesn't get created when there are too many VMs
- Dominant language
- Go
- Stars
- 52
- Forks
- 34
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 1
Description
When the number of VMs are higher than the `default.page.size` global setting in CloudStack (defaults to 500), the load balancer doesn't get created and it fails with this error in the logs:
```
E0713 01:20:25.311237 1 controller.go:310] error processing service default/test-svc (will retry): failed to ensure load balancer: none of the hosts matched the list of VMs retrieved from CS API
```
As a work around, increasing `default.page.size` works for now.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at controller.go:310 and trace the CloudStack API request that retrieves VMs while ensuring the load balancer for a service. Check how the default.page.size limit affects that retrieval. Done means a load balancer is created successfully when the VM count exceeds the default page size without requiring a setting change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100