kubernetes/kops · error
failed to find server with id ("%s"): %v
Error message
failed to find server with id ("%s"): %v What it means
While collecting a server's floating IPs, the GetInstance lookup for the instance failed. The retry-with-backoff loop returns immediately with this error, meaning the server could not be fetched by ID — typically the instance was deleted mid-operation or the API call failed.
Source
Thrown at upup/pkg/fi/cloudup/openstack/instance.go:152
if err != nil {
return server, err
} else if done {
return server, nil
} else {
return server, wait.ErrWaitTimeout
}
}
func (c *openstackCloud) ListServerFloatingIPs(instanceID string) ([]*string, error) {
return listServerFloatingIPs(c, instanceID, c.floatingEnabled)
}
func listServerFloatingIPs(c OpenstackCloud, instanceID string, floatingEnabled bool) ([]*string, error) {
var result []*string
_, err := vfs.RetryWithBackoff(floatingBackoff, func() (bool, error) {
server, err := c.GetInstance(instanceID)
if err != nil {
return true, fmt.Errorf("failed to find server with id (\"%s\"): %v", instanceID, err)
}
var addresses map[string][]Address
err = mapstructure.Decode(server.Addresses, &addresses)
if err != nil {
return true, err
}
for _, addrList := range addresses {
for _, props := range addrList {
if floatingEnabled {
if props.IPType == "floating" {
result = append(result, new(props.Addr))
}
} else {
result = append(result, new(props.Addr))
}
}View on GitHub (pinned to 4c8573c808)
Solutions
- Confirm the instance still exists: openstack server show <id>
- Retry if the failure was a transient API error
- If the instance was deleted, abandon the floating-IP lookup
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at upup/pkg/fi/cloudup/openstack/instance.go:152 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/59fa0a860b8e2679.
Report an issue: GitHub.