kubernetes/kops · error

error listing keypairs: %v

Error message

error listing keypairs: %v

What it means

Listing keypairs via the Nova API failed while fetching all pages. The read is wrapped in retry-with-backoff, so this indicates a persistent API failure such as credential, endpoint, or service problems.

Source

Thrown at upup/pkg/fi/cloudup/openstack/keypair.go:111

	if err != nil {
		return err
	} else if done {
		return nil
	} else {
		return wait.ErrWaitTimeout
	}
}

func (c *openstackCloud) ListKeypairs() ([]keypairs.KeyPair, error) {
	return listKeypairs(c)
}

func listKeypairs(c OpenstackCloud) ([]keypairs.KeyPair, error) {
	var k []keypairs.KeyPair
	done, err := vfs.RetryWithBackoff(readBackoff, func() (bool, error) {
		allPages, err := keypairs.List(c.ComputeClient(), nil).AllPages(context.TODO())
		if err != nil {
			return false, fmt.Errorf("error listing keypairs: %v", err)
		}

		ks, err := keypairs.ExtractKeyPairs(allPages)
		if err != nil {
			return false, fmt.Errorf("error extracting keypairs from pages: %v", err)
		}
		k = ks
		return true, nil
	})
	if err != nil {
		return k, err
	} else if done {
		return k, nil
	} else {
		return k, wait.ErrWaitTimeout
	}
}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Check OpenStack compute API reachability and credentials
2. Verify the nova endpoint in the catalog
3. Retry once service health is restored

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/openstack/keypair.go:111 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/492f988f690864f9. Report an issue: GitHub.