kubernetes/kops · error
Multiple servers found with name %s
Error message
Multiple servers found with name %s
What it means
Instance discovery matched more than one server whose name or 'kops name' metadata equals the expected instance name. The name-to-server mapping must be unique; duplicates make it ambiguous which server represents the task, often caused by leftover servers from a previous cluster or manual copies.
Source
Thrown at upup/pkg/fi/cloudup/openstacktasks/instance.go:190
continue
}
metadataName := ""
val, ok = server.Metadata[openstack.TagKopsName]
if ok {
metadataName = val
}
// name or metadata tag should match to instance name
// this is needed for backwards compatibility
if server.Name == fi.ValueOf(e.Name) || metadataName == fi.ValueOf(e.Name) {
filteredList = append(filteredList, server)
}
}
if filteredList == nil {
return nil, nil
}
if len(filteredList) > 1 {
return nil, fmt.Errorf("Multiple servers found with name %s", fi.ValueOf(e.Name))
}
server := filteredList[0]
actual := &Instance{
ID: new(server.ID),
Name: e.Name,
SSHKey: new(server.KeyName),
Lifecycle: e.Lifecycle,
Metadata: server.Metadata,
Role: new(server.Metadata["KopsRole"]),
AvailabilityZone: e.AvailabilityZone,
GroupName: e.GroupName,
ConfigDrive: e.ConfigDrive,
Status: new(server.Status),
}
ports, err := cloud.ListPorts(ports.ListOpts{
DeviceID: server.ID,View on GitHub (pinned to 4c8573c808)
Solutions
- List servers matching the name and inspect their k8s/kops metadata tags
- Delete or rename stale duplicate servers
- Re-run discovery once names are unique
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at upup/pkg/fi/cloudup/openstacktasks/instance.go:190 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/68864011a0ab019c.
Report an issue: GitHub.