kubernetes/kops · error

load balancer service get request returned error %v

Error message

load balancer service get request returned error %v

What it means

Wraps the DigitalOcean load-balancer Get-by-ID failure in Find. Fires when the DO API errors while fetching the LB referenced by its stored ID (auth, connectivity, or a stale ID for a deleted LB that is not reported as 404).

Source

Thrown at upup/pkg/fi/cloudup/dotasks/loadbalancer.go:82

	_ fi.HasAddress    = &LoadBalancer{}
)

func (lb *LoadBalancer) CompareWithID() *string {
	return lb.ID
}

func (lb *LoadBalancer) Find(c *fi.CloudupContext) (*LoadBalancer, error) {
	klog.V(10).Infof("load balancer FIND - ID=%s, name=%s", fi.ValueOf(lb.ID), fi.ValueOf(lb.Name))
	if fi.ValueOf(lb.ID) == "" {
		// Loadbalancer = nil if not found
		return nil, nil
	}

	cloud := c.T.Cloud.(do.DOCloud)
	lbService := cloud.LoadBalancersService()
	loadbalancer, _, err := lbService.Get(context.TODO(), fi.ValueOf(lb.ID))
	if err != nil {
		return nil, fmt.Errorf("load balancer service get request returned error %v", err)
	}

	return &LoadBalancer{
		Name:    new(loadbalancer.Name),
		ID:      new(loadbalancer.ID),
		Region:  new(loadbalancer.Region.Slug),
		VPCUUID: new(loadbalancer.VPCUUID),

		// Ignore system fields
		Lifecycle:         lb.Lifecycle,
		WellKnownServices: lb.WellKnownServices,
	}, nil
}

func (lb *LoadBalancer) Run(c *fi.CloudupContext) error {
	return fi.CloudupDefaultDeltaRunMethod(lb, c)
}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Check the wrapped DO API error for the status code
2. Verify the LB still exists (doctl compute load-balancer list)
3. Reconcile stale state if the LB was deleted outside kops

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/dotasks/loadbalancer.go:82 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of kubernetes/kops@4c8573c808 (2026-09-05). Data as JSON: /api/errors/e7c4dfa06d433fc5. Report an issue: GitHub.