kubernetes/kops · error

failed to delete L3 floating ip %s: %v

Error message

failed to delete L3 floating ip %s: %v

What it means

deleteL3FloatingIP wraps the l3floatingip.Delete ExtractErr failure (via the networking client) when releasing a layer-3 floating IP. NotFound is tolerated; other API errors fire this message and are retried with the write backoff before surfacing.

Source

Thrown at upup/pkg/fi/cloudup/openstack/floatingip.go:124

			return true, nil
		}
		return false, nil
	})
	if !done && err == nil {
		err = wait.ErrWaitTimeout
	}
	return err
}

func (c *openstackCloud) DeleteL3FloatingIP(id string) (err error) {
	return deleteL3FloatingIP(c, id)
}

func deleteL3FloatingIP(c OpenstackCloud, id string) (err error) {
	done, err := vfs.RetryWithBackoff(writeBackoff, func() (bool, error) {
		err = l3floatingip.Delete(context.TODO(), c.NetworkingClient(), id).ExtractErr()
		if err != nil && !isNotFound(err) {
			return false, fmt.Errorf("failed to delete L3 floating ip %s: %v", id, err)
		}
		return true, nil
	})
	if !done && err == nil {
		err = wait.ErrWaitTimeout
	}
	return err
}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Verify the floating IP ID exists in the Neutron project
2. Check Networking API credentials and scopes
3. Retry; the operation already runs inside RetryWithBackoff

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/openstack/floatingip.go:124 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/c324e3123d6acc19. Report an issue: GitHub.