kubernetes/kops · error
could not find floating ip associated to server ("%s") %v
Error message
could not find floating ip associated to server ("%s") %v What it means
After polling a server's addresses, no floating IP (or, when floating IPs are disabled, no address at all) was found, or the polling errored/timed out. The server either has not yet received its addresses or genuinely has none associated in the observed address map.
Source
Thrown at upup/pkg/fi/cloudup/openstack/instance.go:178
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))
}
}
}
if len(result) > 0 {
return true, nil
}
return false, nil
})
if len(result) == 0 || err != nil {
return result, fmt.Errorf("could not find floating ip associated to server (\"%s\") %v", instanceID, err)
}
return result, nil
}
func (c *openstackCloud) DeleteInstance(i *cloudinstances.CloudInstance) error {
return deleteInstance(c, i)
}
func deleteInstance(c OpenstackCloud, i *cloudinstances.CloudInstance) error {
return deleteInstanceWithID(c, i.ID)
}
func (c *openstackCloud) DeleteInstanceWithID(instanceID string) error {
return deleteInstanceWithID(c, instanceID)
}
func deleteInstanceWithID(c OpenstackCloud, instanceID string) error {
done, err := vfs.RetryWithBackoff(deleteBackoff, func() (bool, error) {View on GitHub (pinned to 4c8573c808)
Solutions
- Check the server's addresses in OpenStack and confirm a floating IP is associated
- If networking is slow, retry — the lookup polls with backoff
- For floating-enabled clusters, associate a floating IP to the port
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at upup/pkg/fi/cloudup/openstack/instance.go:178 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/ff69123fe38dc238.
Report an issue: GitHub.