kubernetes/kops · error

failed to list L3 floating ip: %v

Error message

failed to list L3 floating ip: %v

What it means

listL3FloatingIPs wraps the l3floatingip.List AllPages failure when enumerating Neutron layer-3 floating IPs. It fires when the list API call fails (auth, throttling, network) and is retried with backoff before surfacing.

Source

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

	})
	if !done {
		if err == nil {
			err = wait.ErrWaitTimeout
		}
		return fip, err
	}
	return fip, nil
}

func (c *openstackCloud) ListL3FloatingIPs(opts l3floatingip.ListOpts) (fips []l3floatingip.FloatingIP, err error) {
	return listL3FloatingIPs(c, opts)
}

func listL3FloatingIPs(c OpenstackCloud, opts l3floatingip.ListOpts) (fips []l3floatingip.FloatingIP, err error) {
	done, err := vfs.RetryWithBackoff(readBackoff, func() (bool, error) {
		page, err := l3floatingip.List(c.NetworkingClient(), opts).AllPages(context.TODO())
		if err != nil {
			return false, fmt.Errorf("failed to list L3 floating ip: %v", err)
		}
		fips, err = l3floatingip.ExtractFloatingIPs(page)
		if err != nil {
			return false, fmt.Errorf("failed to extract L3 floating ip: %v", err)
		}
		return true, nil
	})
	if !done {
		if err == nil {
			err = wait.ErrWaitTimeout
		}
		return fips, err
	}
	return fips, nil
}

func (c *openstackCloud) DeleteFloatingIP(id string) (err error) {
	return deleteFloatingIP(c, id)

View on GitHub (pinned to 4c8573c808)

Solutions

  1. Check Neutron API credentials and connectivity
  2. Retry; the operation already runs inside RetryWithBackoff
  3. Review list filter options if the query is rejected
Defensive patterns

Strategy: retry

When it happens

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