kubernetes/kops · error

could not find address for %v,

Error message

could not find address for %v, 

What it means

dumpNode could not determine an address to connect to for the named node: the registered Node object exposes no usable IP. (The message format has a trailing-space quirk.)

Source

Thrown at pkg/dump/dumper.go:301

	if len(node.PrivateAddresses) > 0 {
		return node.PrivateAddresses[0], d.dumpNode(ctx, node.PrivateAddresses[0], node.PrivateAddresses[0], true)
	}
	return "", fmt.Errorf("no known addresses for node %s", node.Name)
}

// defaultNodeDumpTimeout bounds the time spent connecting to and dumping a single node.
// A healthy node dumps in well under a minute. Without this cap, an SSH operation
// against an unreachable node blocks until the OS TCP timeout (~15 min) expires.
// Large clusters dump multi-GB logs per node and need a higher value, configurable
// via the --node-dump-timeout flag, because the files are dumped sequentially and a
// single oversized log can otherwise exhaust the budget before the rest are read.
const defaultNodeDumpTimeout = time.Minute

// DumpNode connects to a node and dumps the logs.
func (d *logDumper) dumpNode(ctx context.Context, name string, ip string, useBastion bool) error {
	if ip == "" {
		return fmt.Errorf("could not find address for %v, ", name)
	}

	klog.Infof("Dumping node %s", name)

	ctx, cancel := context.WithTimeout(ctx, d.nodeDumpTimeout)
	defer cancel()

	n, err := d.connectToNode(ctx, name, ip, useBastion)
	if err != nil {
		return fmt.Errorf("connecting: %w", err)
	}

	// As long as we connect to the node we will not return an error;
	// a failure to collect a log (or even any logs at all) is not
	// considered an error in dumping the node.
	// TODO(justinsb): clean up / rationalize
	errors := n.dump(ctx)
	for _, e := range errors {

View on GitHub (pinned to 4c8573c808)

Solutions

1. Check the Node object's status.addresses in the cluster
2. Verify the node is Ready and has reported its internal IP
3. Fall back to the cloud instance's addresses if the Node status is stale

When it happens

Trigger: Thrown at pkg/dump/dumper.go:301 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/cd2c9c6765251884. Report an issue: GitHub.