kubernetes/kops · error
error deleting instance of group %s: %w
Error message
error deleting instance of group %s: %w
What it means
In RenderScw's scale-down loop, DeleteServer failed for one of the surplus instances selected for removal (taken from the head of the group's server list). The instance group name identifies the group; the wrapped error explains the deletion failure (locked server, API error).
Source
Thrown at upup/pkg/fi/cloudup/scalewaytasks/instance.go:299
})
if err != nil {
return fmt.Errorf("error waiting for instance %s of group %q: %w", srv.Server.ID, fi.ValueOf(expected.Name), err)
}
}
// If newInstanceCount < 0, we need to delete instances of this group
if newInstanceCount < 0 {
igInstances, err := t.Cloud.GetClusterServers(t.Cloud.ClusterName(actual.Tags), actual.Name)
if err != nil {
return fmt.Errorf("error deleting instance: %w", err)
}
for i := 0; i > newInstanceCount; i-- {
toDelete := igInstances[i*-1]
err = t.Cloud.DeleteServer(toDelete)
if err != nil {
return fmt.Errorf("error deleting instance of group %s: %w", toDelete.Name, err)
}
}
}
return nil
}
type terraformInstanceIP struct {
Tags []string `cty:"tags"`
}
type terraformInstance struct {
Name *string `cty:"name"`
IPID *terraformWriter.Literal `cty:"ip_id"`
Type *string `cty:"type"`
Tags []string `cty:"tags"`
Image *string `cty:"image"`
UserData map[string]*terraformWriter.Literal `cty:"user_data"`View on GitHub (pinned to 4c8573c808)
Solutions
- Check the wrapped error for the delete failure
- Verify the server is not locked or in transition
- Retry the apply; already-deleted servers are tolerated by DeleteServer's 404 handling
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at upup/pkg/fi/cloudup/scalewaytasks/instance.go:299 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/48918351b1fbb5c6.
Report an issue: GitHub.