kubernetes/kops · error

error setting metadata on instance: %v

Error message

error setting metadata on instance: %v

What it means

Wrapped error from Instance.RenderGCE when the Instances.SetMetadata API call fails while updating metadata on an existing instance. Often caused by a stale metadata fingerprint (concurrent modification) or a permissions/API error.

Source

Thrown at upup/pkg/fi/cloudup/gcetasks/instance.go:341

	i, err := e.mapToGCE(project, ipAddressResolver)
	if err != nil {
		return err
	}

	if a == nil {
		klog.V(2).Infof("Creating instance %q", i.Name)
		if _, err := cloud.Compute().Instances().Insert(project, zone, i); err != nil {
			return fmt.Errorf("error creating Instance: %v", err)
		}
	} else {
		if changes.Metadata != nil {
			klog.V(2).Infof("Updating instance metadata on %q", i.Name)

			i.Metadata.Fingerprint = a.metadataFingerprint

			op, err := cloud.Compute().Instances().SetMetadata(project, zone, i.Name, i.Metadata)
			if err != nil {
				return fmt.Errorf("error setting metadata on instance: %v", err)
			}

			if err := cloud.WaitForOp(op); err != nil {
				return fmt.Errorf("error setting metadata on instance: %v", err)
			}

			changes.Metadata = nil
		}

		if !changes.isZero() {
			klog.Errorf("Cannot apply changes to Instance: %v", changes)
			return fmt.Errorf("cannot apply changes to Instance: %v", changes)
		}
	}

	return nil
}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Retry the apply — stale fingerprint errors resolve once Find() refreshes the fingerprint
2. Check for concurrent mutations of instance metadata (autoscaler, config agent, manual gcloud)
3. Inspect the wrapped error for permission or API issues

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/gcetasks/instance.go:341 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/296441a74ba6d80b. Report an issue: GitHub.